Hi Junio,
On Wed, 27 Jan 2016, Junio C Hamano wrote:
> Johannes Schindelin writes:
>
> > On Tue, 26 Jan 2016, Junio C Hamano wrote:
> >
> >> Johannes Schindelin writes:
> >>
> >> > -git checkout -b @/at-test &&
> >> > +if ! test_have_prereq MINGW
> >> > +then
> >> > +
Hi Junio,
On Wed, 27 Jan 2016, Junio C Hamano wrote:
> Johannes Schindelin writes:
>
> [administrivia: I finally managed to correct e-mail address of peff@,
> which has been giving me bounces for all the previous messages in
> the thread]
Oops! I got those bounces myself, but wrote them off to
On Wed, Jan 27, 2016 at 12:49:31PM -0800, Junio C Hamano wrote:
> Junio C Hamano writes:
>
> > I wonder what would break if we ask this question instead:
> >
> > We do not know if the working tree file and the indexed data
> > match. Let's see if "git checkout" of that path would leave t
On 01/27/2016 08:05 PM, Junio C Hamano wrote:
(Changed the topic, 2 notes inside)
Clemens Buchacher writes:
Coming back to "[PATCH] optionally disable gitattributes": The topics
are related, because they both deal with the situation where the work
tree has files which are not normalized accord
On 28 January 2016 at 11:40, Moritz Neeb wrote:
> I suppose just fixing/revising this would be kind
> of a too low hanging fruit?
I am in no way qualified to speak to the majority of your post, but I
can't imagine anyone refusing your work because it was 'too low
hanging fruit'.
Indeed, the gene
On 01/28/2016 03:56 AM, David A. Greene wrote:
Marcus Brinkmann writes:
With my patch, "git subtree split -P" produces the same result (for my
data set) as "git filter-branch --subdirectory-filter", which is much
faster, because it selects the revisions to rewrite before rewriting.
As I am not
Dear Sir/Madam,
Clean tested working pulls CPUs and QTYs in stock.
115 X X5650
65 X E5410
75 X X5660
145 X E5530
100 X E5645
40 X X5680
75 X X5690
Brand new sealed IP phones and QTYs in stock.
55 x CP-7937G
77 x CP-7942G
54 x CP-7945G
75 x CP-7962G
..
45 x Avaya 9630
6
Marcus Brinkmann writes:
> With my patch, "git subtree split -P" produces the same result (for my
> data set) as "git filter-branch --subdirectory-filter", which is much
> faster, because it selects the revisions to rewrite before rewriting.
> As I am not using any of the advanced features of "gi
[ Sorry it took a few days to reply. I am absolutely slammed at work
and will be for the next few weeks at least. The good news is that
it's resulting in some nice work on git-subtree! :) ]
Marcus Brinkmann writes:
> On 01/20/2016 05:05 AM, David A. Greene wrote:
>> Marcus Brinkmann writ
Hi,
I looked at this patch series again and fixed all memory leaks as found by
coverity scan.
This applies on top of sb/submodule-parallel-update
Thanks,
Stefan
Interdiff to v3:
diff --git a/builtin/submodule--helper.c b/builtin/submodule--helper.c
index c9b0c05..dd8b2a5 100644
--- a/builtin/su
Later on we want to automatically call `git submodule init` from
other commands, such that the users don't have to initialize the
submodule themselves. As these other commands are written in C
already, we'd need the init functionality in C, too. The
`resolve_relative_url` function is a large part
By having the `init` functionality in C, we can reference it easier
from other parts in the code.
Signed-off-by: Stefan Beller
Signed-off-by: Junio C Hamano
---
builtin/submodule--helper.c | 119 ++--
git-submodule.sh| 39 +--
2 f
On Wed, Jan 27, 2016 at 4:40 PM, Moritz Neeb wrote:
> Hi git developers,
>
> the next Google Summer of Code is not too far away. I expect git to
> apply for it and hopefully have some student spots which in turn I plan
> to apply. It was recommended elsewhere and on this list as well, that it
> is
Hi git developers,
the next Google Summer of Code is not too far away. I expect git to
apply for it and hopefully have some student spots which in turn I plan
to apply. It was recommended elsewhere and on this list as well, that it
is beneficial to engage with the community early, that's why I am
From: "Junio C Hamano"
Jonathan Smith writes:
It's pretty clear that code stored in a Git repository isn't
considered a derived work of Git, regardless of whether it is used
in a commercial context or otherwise.
I'm guessing here, but I suspect that while its 'pretty clear' to Jonathan,
th
Junio C Hamano writes:
> @@ -598,9 +597,9 @@ static int run_argv(int *argcp, const char ***argv)
>*/
> if (done_alias)
> break;
> + done_alias = 1;
> if (!handle_alias(argcp, argv))
> break;
> -
Hallo René,
On Wed, Jan 27, 2016 at 09:31:15PM +0100, René Scharfe wrote:
> Hello Robert,
>
> it's customary to discuss in the open by copying the list. Unless
> there are secrets involved, but I don't see any below. I kept it
> private anyway in case I missed any, but please cc:
> git@vger.ker
The only code that cares about the value of the global variable
saved_env_before_alias after the previous fix is handle_builtin()
that turns into a glorified no-op when the variable is true, so the
logic could safely be lifted to its caller, i.e. the caller can
refrain from calling it when the vari
On Tue, Jan 26, 2016 at 11:06:25PM +0100, René Scharfe wrote:
> Am 24.01.2016 um 16:59 schrieb f...@fuz.su:
> >Right now, git archive creates a pax global header of the form
> >
> > comment=57ca140635bf157354124e4e4b3c8e1bde2832f1
> >
> >in tar archives it creates. This is suboptimal as as comm
We made sure that save_env_before_alias() does not skip saving the
environment when asked to (which led to use-after-free of orig_cwd
in restore_env() in the buggy version) with the previous step.
Protect against future breakage where somebody adds new callers of
these functions in an unbalanced f
Junio C Hamano writes:
> Duy Nguyen writes:
>
>> On Wed, Jan 27, 2016 at 1:49 PM, Junio C Hamano wrote:
>>> Junio C Hamano writes:
>>>
I spoke too soon, I am afraid.
...
I wonder if this would be better done as a multi-part series that
goes like this:
...
>>>
>>> So he
On Wed, Jan 27, 2016 at 09:49:38PM +, Charles Bélanger wrote:
> Here's the git clone command launch by a .sh script file called from
> ~/.profile:
> git clone https://myusern...@bitbucket.org/CompanyName/ProjectName.git
> ~/Projects/SubFolderName/ProjectName
>
> Here's the error from bash .
Nguyễn Thái Ngọc Duy writes:
> For any worktree, the new file .git/common/config is read first, then
> either .git/config or .git/worktrees/xxx/config is read after. There's
> no special per-worktree var list any more. Which is great. You want to
> add per-worktree config vars, use "git config -
Nguyễn Thái Ngọc Duy writes:
> ($C stands for $GIT_COMMON_DIR for the rest of the message)
>
> In main worktree, we read these config files in this order:
>
> 1) system config
> 2) XDG config
> 3) user config
> 4) $GIT_DIR/config
>
> Currently linked worktrees share the same config file at step
Nguyễn Thái Ngọc Duy writes:
> +static struct common_dir common_list_v1[] = {
> + ...
> +};
> +
> +static struct common_dir *get_common_list(void)
> +{
> + switch (repository_format_worktree_version) {
> + case 0: return common_list_v0;
> + case 1: return common_list_v1;
Why not
Nguyễn Thái Ngọc Duy writes:
> Multiple worktree setup is still evolving and its behavior may be
> changed in future. But we do not want to break existing worktree
s/be changed/change/
> setups. A new set of extensions, worktree=X, is recognized to tell Git
> what multiple worktree "version" i
Hello Git Community,
I'm working at AddEnergie at Quebec city in Canada and I'm currently working on
making a Build Server in a Virtual Machine running Ubuntu.
We are using git for our source code and I'm the first one here that need to
use git store credentials for an Automated Build Server tha
Junio C Hamano writes:
> One way to solve (1) I can think of is to change the definition of
> ce_compare_data(), which is called by the code that does not trust
> the cached stat data (including but not limited to the Racy Git
> codepath). The current semantics of that function asks this
> quest
Eric Wong writes:
> Junio C Hamano wrote:
>> I am not sure if it is a good idea to show */*/* as an example in
>> the message (that is an anti-example of 'one set of wildcard' by
>> having three stars, isn't it?), but that is not a new issue this
>> change introduces.
>
> Actually, going back to
Johannes Schindelin writes:
> I made a couple of other adjustments anyway, so expect a new iteration
> shortly. This time cross-checked on Linux.
Thanks, will take a look.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More
Johannes Schindelin writes:
> Hi Junio,
>
> On Tue, 26 Jan 2016, Junio C Hamano wrote:
>
>> Johannes Schindelin writes:
>>
>> > @@ -35,7 +35,10 @@ test_expect_success 'setup' '
>> >git checkout -b upstream-branch &&
>> >test_commit upstream-one &&
>> >test_commit upstream-two &&
>>
Thanks, will queue after looking at the interdiff since v4.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Wed, Jan 27, 2016 at 09:09:31PM +0100, Michael J Gruber wrote:
> "subkey" and "uid" are different things. You bind a subkey to your
> primary key with that self-signature. subkeys don't carry any other
> signatures.
>
> A primary key "carries" the uids, and whenever someone "signs your key"
>
Junio C Hamano venit, vidit, dixit 27.01.2016 19:10:
> Michael J Gruber writes:
>
>> Jeff King venit, vidit, dixit 27.01.2016 09:09:
>>
>>> The bigger issue is that gpg seems to give us only _one_ uid, when there
>>> may be several. E.g., Junio's v2.7.0 is signed by 96AFE6CB, which is a
>>> sub-k
Johannes Schindelin writes:
[administrivia: I finally managed to correct e-mail address of peff@,
which has been giving me bounces for all the previous messages in
the thread]
> Your response is also an indicator to me that future myself will find the
> same code just as confusing as you did, th
Hi Junio,
On Wed, 27 Jan 2016, Junio C Hamano wrote:
> Johannes Schindelin writes:
>
> >> Just in case it was unclear, none of the comment above means I want
> >> any part of the patch redone--I am happy with this patch as-is.
> >
> > Thanks for saying that... I was about to try to make things
Clemens Buchacher writes:
> Coming back to "[PATCH] optionally disable gitattributes": The topics
> are related, because they both deal with the situation where the work
> tree has files which are not normalized according to gitattributes. But
> my patch is more about saying: ok, I know I may hav
Johannes Schindelin writes:
>> Just in case it was unclear, none of the comment above means I want
>> any part of the patch redone--I am happy with this patch as-is.
>
> Thanks for saying that... I was about to try to make things clearer, but I
> could not think of a better term than "needs_cr".
Michael J Gruber writes:
> Jeff King venit, vidit, dixit 27.01.2016 09:09:
>
>> The bigger issue is that gpg seems to give us only _one_ uid, when there
>> may be several. E.g., Junio's v2.7.0 is signed by 96AFE6CB, which is a
>> sub-key that has several uids associated with it. The one that "git
On Wed, Jan 27, 2016 at 12:46 AM, Lars Schneider
wrote:
>
> On 26 Jan 2016, at 23:58, Junio C Hamano wrote:
>
>> Lars Schneider writes:
>>
>>> Hi Junio,
>>>
>>> Did you miss the topic "submodule: extend die message on failed
>>> checkout with depth argument" or do you not agree with it
>>> ($gma
When merging files with CR/LF line endings, the conflict markers should
match those, lest the output file has mixed line endings.
This is particularly of interest on Windows, where some editors get
*really* confused by mixed line endings.
The original version of this patch by Beat Bolli respected
The original patch was sent by Beat Bolli in
http://thread.gmane.org/gmane.comp.version-control.git/281600
My suggestion to extend it to respect gitattributes led to
changes that broke the original patch. And they were misguided
to begin with (see below).
Since there have been a couple of "What's
In the previous patch, we made sure that the conflict markers themselves
match the end-of-line style of the input files. However, this still left
out the conflicting text itself: if it lacks a trailing newline, we
add one, and should add a carriage return when appropriate, too.
Signed-off-by: Joha
Hi Junio,
On Wed, 27 Jan 2016, Johannes Schindelin wrote:
> --8323329-1704809497-1453911609=:2964
> Content-Type: text/plain; charset=X-UNKNOWN
Oh well. I guess I am really too stupid to get this right... Will change
my script to call format-patch with the --add-header='Content-Type:
text/plain;
MSYS2 (the POSIX emulation layer used by Git for Windows' Bash) actually
has a working mkfifo. The only problem is that it is only emulating
named pipes through the MSYS2 runtime; The Win32 API has no idea about
named pipes, hence the Git executable cannot access those pipes either.
The symptom is
This solves two problems:
- we now have proper localisation even on Windows
- we sidestep the infamous "BUG: your vsnprintf is broken (returned -1)"
message when running "git init" (which otherwise prevents the entire
test suite from running) because libintl.h overrides vsnprintf() with
lib
This test assumed that there is only one directory separator (the
forward slash), not two equivalent directory separators.
However, on Windows, the back slash and the forward slash *are*
equivalent.
Let's paper over this issue by converting the backward slashes to
forward ones in the test that fai
POSIX semantics requires lstat() to fail with ENOTDIR when "[a]
component of the path prefix names an existing file that is neither a
directory nor a symbolic link to a directory".
See http://pubs.opengroup.org/onlinepubs/9699919799/functions/lstat.html
This behavior is expected by t1404-update-r
The Git daemon tests create a FIFO first thing and will hang if said
FIFO is not available.
This is a problem with Git for Windows, where `mkfifo` is an MSYS2
program that leverages MSYS2's POSIX emulation layer, but
`git-daemon.exe` is a MINGW program that has not the first clue about
that POSIX
Since baaf233 (connect: improve check for plink to reduce false
positives, 2015-04-26), t5601 writes out a `plink.exe` for testing that
is actually a shell script. So the assumption that the `.exe` extension
implies that the file is *not* a shell script is now wrong.
Since there was no love for th
In Git for Windows' SDK, the tests are run using a Bash that relies on
the POSIX emulation layer MSYS2 (itself a friendly fork of Cygwin). As
such, paths in tests can be POSIX paths. As soon as those paths are
passed to git.exe (which does *not* use the POSIX emulation layer),
those paths are conve
From: Pat Thoyts
The colon is used by check-ignore to separate paths from other output
values. If we use an absolute path, however, on Windows it will be
converted into a Windows path that very much contains a colon.
It is actually not at all necessary to make the path of the global
excludes abs
In Git for Windows, the MSYS2 POSIX emulation layer used by the Bash
converts command-line arguments that looks like they refer to a POSIX
path containing a file list (i.e. @) into a Windows path
equivalent when calling non-MSYS2 executables, such as git.exe.
Let's just skip the test that uses the
On Windows, absolute paths never start with a slash, unless a POSIX
emulation layer is used. The latter is the case for MSYS2's Perl that
Git for Windows leverages. However, in the tests we also go through
plain `git.exe`, which does *not* leverage the POSIX emulation layer,
and therefore the paths
When shell scripts access a $TMPDIR variable containing backslashes,
they will be mistaken for escape characters. Let's not let that happen
by converting them to forward slashes.
This partially fixes t7800 with MSYS2.
Signed-off-by: Johannes Schindelin
---
compat/mingw.c | 23 ++
It does not quite work because it produces DOS line endings which the
shell does not like at all.
This lets t0200-gettext-basic.sh, t0204-gettext-reencode-sanity.sh,
t3406-rebase-message.sh, t3903-stash.sh, t7400-submodule-basic.sh,
t7401-submodule-summary.sh, t7406-submodule-update.sh and
t7407-s
On Windows, Git itself has no clue about POSIX paths, but its shell
scripts do. In this instance, we get mixed paths as a result, and when
comparing the path of the author file, we get a mismatch that is
entirely due to the POSIX path vs Windows path clash.
Let's just skip this test so that t9130-
This is a big milestone. With these modifications, Git's source code
does not only build without warnings in Git for Windows' SDK, but
passes the entire regression test suite.
The patch series contains three different types of patches. First,
there are a couple of real fixes that were triggered by
From: Karsten Blees
We will add more environment-related code to that new function
in the next patch.
Signed-off-by: Karsten Blees
Signed-off-by: Johannes Schindelin
---
compat/mingw.c | 30 +-
1 file changed, 17 insertions(+), 13 deletions(-)
diff --git a/compat/
From: =?UTF-8?q?=EB=A7=88=EB=88=84=EC=97=98?=
When the rename() function tries to move a directory it fails if the
target directory exists. It should check if it can delete the (possibly
empty) target directory and then try again to move the directory.
This partially fixes t9100-git-svn-basic.sh
On Windows, the permission system works completely differently than
expected by some of the tests. So let's make sure that we do not test
POSIX functionality on Windows.
This lets t9124-git-svn-dcommit-auto-props.sh pass in Git for Windows'
SDK.
Signed-off-by: Johannes Schindelin
---
t/t9124-gi
Many a test requires either POSIXPERM (to change the executable bit) or
SYMLINKS, and neither are available on Windows.
This lets t9100-git-svn-basic.sh pass in Git for Windows' SDK.
Signed-off-by: Johannes Schindelin
---
t/t9100-git-svn-basic.sh | 18 +-
1 file changed, 9 inser
On Windows, there are no POSIX paths, only Windows ones (an absolute
Windows path looks like "C:\Program Files\Git\ReleaseNotes.html", under
most circumstances, forward slashes are also allowed and synonymous to
backslashes).
So when a POSIX shell (such as MSYS2's Bash, which is used by Git for
Wi
On Windows' file systems, file names with trailing dots are forbidden.
The POSIX emulation layer used by Git for Windows' Subversion emulates
those file names, therefore the test adding the file would actually
succeed, but when we would ask git.exe (which does not leverage the
POSIX emulation layer
MSYS2 actually allows to create files or directories whose names contain
tabs, newlines or colors, even if plain Win32 API cannot access them.
As we are using an MSYS2 bash to run the tests, such files or
directories are created successfully, but Git itself has no chance to
work with them because i
Hi Junio,
On Tue, 26 Jan 2016, Junio C Hamano wrote:
> Johannes Schindelin writes:
>
> > @@ -181,7 +180,8 @@ test_expect_success "$name" '
> > name="commit with UTF-8 message: locale: $GIT_SVN_LC_ALL"
> > LC_ALL="$GIT_SVN_LC_ALL"
> > export LC_ALL
> > -test_expect_success UTF8 "$name" "
> >
Hi Andrey,
we never saw the two mails you were replying to, and please note that 1)
the preferred place to report bugs in Git for Windows is
https://github.com/git-for-windows/git/issues, as outlined in
https://git-for-windows.github.io/#contribute, and that 2) top-posting
will most likely result
On Wed, Jan 27, 2016 at 04:04:39PM +0100, Torsten Bögershausen wrote:
>
> It feels like a workaround for something that could be fixable, or is already
> ongoing.
> Before going into more details,
> could you tell us which attributes you are typically using (when having this
> problems) ?
> Is it
I think Junio pointed me to this thread from "[PATCH] optionally disable
gitattributes". Since I am not sure I am following everything correctly
in this thread, allow me to recapitulate what I understood so far.
Firstly, I think the racy'ness of t0025 is understood. It is due to the
is_racy_timest
From: Torsten Bögershausen
When a filter is configured, a different code-path is used in convert.c
and entry.c via get_stream_filter(), but there are no test cases yet.
Add tests for the filter API by configuring the ident filter.
The result of the SHA1 conversion is not checked, this is already
https://lab.nexedi.com/kirr/git-backup.git
This program backups files and set of bare Git repositories into one Git
repository.
Files are copied to blobs and then added to tree under certain place, and for
Git repositories, all reachable objects are pulled in with maintaining index
which remember
On 27.01.16 12:59, Junio C Hamano wrote:
> Clemens Buchacher writes:
>
>> If committed files are not normalized, adding gitattributes has the
>> side effect that such files are shown as modified, even though they
>> were not actually modified by the user, and the work tree matches
>> the committe
Additional note - when I use the command line git push doesn't display
any errors but no updates on github...
git status says :
On branch master
Your branch is ahead of 'origin/master' by 3 commits.
On 1/27/2016 2:51 PM, Andrey Chernyshov wrote:
On 1/27/2016 2:35 PM, Andrey Chernyshov wrote:
Duy Nguyen writes:
> On Wed, Jan 27, 2016 at 1:49 PM, Junio C Hamano wrote:
>> Junio C Hamano writes:
>>
>>> I spoke too soon, I am afraid.
>>> ...
>>> I wonder if this would be better done as a multi-part series that
>>> goes like this:
>>> ...
>>
>> So here is the first of the three-patch ser
Clemens Buchacher writes:
> If committed files are not normalized, adding gitattributes has the
> side effect that such files are shown as modified, even though they
> were not actually modified by the user, and the work tree matches
> the committed file. This is because with gitattributes, the f
On 1/27/2016 2:35 PM, Andrey Chernyshov wrote:
On 1/27/2016 2:32 PM, Andrey Chernyshov wrote:
Hi
I'm using PHP storm with git for windows. Once I do a push to the
github I get the following error
Problem signature:
Problem Event Name:APPCRASH
Application Name:git-remote-https.e
Hi Junio,
On Tue, 26 Jan 2016, Junio C Hamano wrote:
> * js/mingw-tests (2016-01-26) 20 commits
> - mingw: skip a test in t9130 that cannot pass on Windows
> - mingw: do not bother to test funny file names
> - mingw: handle the missing POSIXPERM prereq in t9124
> - mingw: avoid illegal filena
Dear Sir or Madam!
please at the top of any page of site click once on the advertising banner,
so that we could pay for hosting our site,
Thank you
ad...@petition.kiev.ua
http://petition.kiev.ua/
добрий день,
просимо на будь-якій сторінці вгорі один раз натиснути на рекламний банер,
щоб ми змогл
If committed files are not normalized, adding gitattributes has the
side effect that such files are shown as modified, even though they
were not actually modified by the user, and the work tree matches
the committed file. This is because with gitattributes, the file is
modified on the fly when git
On 24 Jan 2016, at 22:45, Jeff King wrote:
> On Sun, Jan 24, 2016 at 01:22:50PM +0100, larsxschnei...@gmail.com wrote:
>
>> From: Lars Schneider
>>
>> A clean/smudge filter can be disabled if set to an empty string. However,
>> Git will try to run the empty string as command which results in
On 24 Jan 2016, at 22:35, Eric Sunshine wrote:
> On Sun, Jan 24, 2016 at 10:06 AM, Torsten Bögershausen wrote:
>> On 24.01.16 13:22, larsxschnei...@gmail.com wrote:
>>> From: Lars Schneider
>>> diff --git a/convert.c b/convert.c
>>> @@ -786,7 +786,7 @@ int convert_to_git(const char *path, cons
On 24 Jan 2016, at 16:06, Torsten Bögershausen wrote:
> On 24.01.16 13:22, larsxschnei...@gmail.com wrote:
>> From: Lars Schneider
> Some minor nits inside:
>>
>> A clean/smudge filter can be disabled if set to an empty string.
> "set to an empty string" refers to "git config" (in opposite t
Hi Junio,
On Tue, 26 Jan 2016, Junio C Hamano wrote:
> Johannes Schindelin writes:
>
> > On Windows, the permission system works completely differently than
> > expected by some of the tests. So let's make sure that we do not test
> > POSIX functionality on Windows.
> >
> > This lets t9124-git-
On Wed, Jan 27, 2016 at 1:49 PM, Junio C Hamano wrote:
> Junio C Hamano writes:
>
>> I spoke too soon, I am afraid.
>> ...
>> I wonder if this would be better done as a multi-part series that
>> goes like this:
>> ...
>
> So here is the first of the three-patch series to replace it.
This is much
Jeff King venit, vidit, dixit 27.01.2016 09:09:
> On Wed, Jan 27, 2016 at 08:53:08AM +0100, Michael J Gruber wrote:
>
>>> Yeah, definitely. My thinking was that `verify-tag` could learn a series
>>> of optional consistency checks, enabled by command line options, and
>>> verifying programs (or hum
- This needs to go on top of tb/ls-files-eol
With missing "separate commit", I am having a hard time to decide if
this is something I should pick up at this moment, or I should wait
until that separate commit materializes. What is your intention?
I send a serious including this patch the ne
Hi Junio,
On Tue, 26 Jan 2016, Junio C Hamano wrote:
> Johannes Schindelin writes:
>
> > @@ -35,7 +35,10 @@ test_expect_success 'setup' '
> > git checkout -b upstream-branch &&
> > test_commit upstream-one &&
> > test_commit upstream-two &&
> > - git checkout -b @/at-test &&
> > +
On 26 Jan 2016, at 23:58, Junio C Hamano wrote:
> Lars Schneider writes:
>
>> Hi Junio,
>>
>> Did you miss the topic "submodule: extend die message on failed
>> checkout with depth argument" or do you not agree with it
>> ($gmane/282779)? Stefan Beller reviewed the commits ($gmane/283666
>> a
Hi Junio,
On Tue, 26 Jan 2016, Junio C Hamano wrote:
> Johannes Schindelin writes:
>
> > This is a big milestone. With these modifications, Git's source code
> > does not only build without warnings in Git for Windows' SDK, but
> > passes the entire regression test suite.
>
> Thanks.
>
> With
Hi Eric,
On Tue, 26 Jan 2016, Eric Sunshine wrote:
> On Tue, Jan 26, 2016 at 9:35 AM, Johannes Schindelin
> wrote:
> > MSYS2 actually allows to create files or directories whose names contain
> > tabs, newlines or colors, even if plain Win32 API cannot access them.
> > As we are using an MSYS2 b
On Wed, Jan 27, 2016 at 08:53:08AM +0100, Michael J Gruber wrote:
> > Yeah, definitely. My thinking was that `verify-tag` could learn a series
> > of optional consistency checks, enabled by command line options, and
> > verifying programs (or humans) could turn them on to avoid having to
> > repli
91 matches
Mail list logo
