Hi,
On Thu, 26 Apr 2018, Derrick Stolee wrote:
> On 4/25/2018 1:43 PM, Brandon Williams wrote:
> > On 04/25, Ævar Arnfjörð Bjarmason wrote:
> > > > * bw/protocol-v2 (2018-03-15) 35 commits
> > > > (merged to 'next' on 2018-04-11 at 23ee234a2c)
[... snip ...]
> > > > (this branch is used
Hi,
On Thu, 26 Apr 2018, Elijah Newren wrote:
> On Thu, Apr 26, 2018 at 7:23 PM, Junio C Hamano wrote:
> > Ben Peart writes:
> >
> >> Color me puzzled. :) The consensus was that the default value for
> >> merge.renames come from diff.renames. diff.renames supports copy
> >> detection which me
On Tue, Apr 24, 2018 at 5:56 PM, Thomas Gummerer wrote:
> Thanks Eric for the review and the suggestions on the previous round.
>
> Changes since the previous round:
>
> - UNLEAK new_branch after it was xstrndup'd
> - update the commit message of 2/4 according to Eric's suggestions
> - make force_
On Wed, Apr 25, 2018 at 4:37 AM, Junio C Hamano wrote:
> * tg/worktree-add-existing-branch (2018-04-25) 4 commits
> - worktree: teach "add" to check out existing branches
> - worktree: factor out dwim_branch function
> - worktree: improve message when creating a new worktree
> - worktree: remo
Hi William,
On Thu, 26 Apr 2018, William Chargin wrote:
> Here is a repro script:
>
> #!/bin/sh
> set -eux
> git --version
> tmpdir="$(mktemp -d)"
> cd "${tmpdir}"
> mkdir target repo
> cd repo
> git init
> touch file; git add file
> git commit -m "Initial
Hi,
firstofall: thank all of you for your feedback.
Am Donnerstag, den 26.04.2018, 17:19 -0700 schrieb Elijah Newren:
> On Thu, Apr 26, 2018 at 3:49 AM, Middelschulte, Leif
> wrote:
> > Hi,
> >
> > we're using git-flow as a basic development workflow. However, doing so
> > revealed unexpected
Hi all,
This is a ONE-TIME announcement of Gitwin - a Git Server for Windows:
Gitwin is a packaging of Git, OpenSSH, Nginx and many other related tools to
make it a ready-to-use
solution as a secure git repository on Windows. It supports SSH and HTTP(S)
transports as well as
Gitweb with Highlig
When bisecting a performance regression using a config file,
`./bisect_regression --config my_perf.conf` for example, the
config file can contain Codespeed configuration which would
instruct the 'aggregate.perl' script called by the 'run'
script to output results in the Codespeed format and maybe
t
Hi Dsco,
On Fri, Apr 27, 2018 at 12:23 AM, Johannes Schindelin
wrote:
> Hi,
>
> Guys, you argued long and hard that one config setting (diff.renames)
> should magically imply another one (merge.renames), on the basis that they
> essentially do the same.
I apologize for any frustration; I've pro
Hi,
I'm moving the IRC discussion here, because this might be a bug report
in the end. So, kindly try these steps (103 MB free space required):
$ git clone https://github.com/ClusterLabs/pacemaker.git && cd pacemaker
[...]
$ git branch --contains Pacemaker-0.6.1
* master
$ git tag --merged maste
I have a business proposal in the tune of $10.2 Million USD for you to
handle with me. I have opportunity to transfer this abandon fund to
your bank account in your country which belongs to our client.
I am inviting you in this transaction where this money can be shared
between us at ratio of 60/4
Szia Feri,
> I'm moving the IRC discussion here, because this might be a bug report
> in the end. So, kindly try these steps (103 MB free space required):
>
> $ git clone https://github.com/ClusterLabs/pacemaker.git && cd pacemaker
> [...]
> $ git branch --contains Pacemaker-0.6.1
> * master
> $
Am 12.04.2018 um 21:36 schrieb Martin Ågren:
> On 11 April 2018 at 23:08, Andreas Heiduk wrote:
>> - reflow some paragraphs
>> ---
>> Documentation/githooks.txt | 14 +++---
>> 1 file changed, 7 insertions(+), 7 deletions(-)
>
> I have reviewed the resulting githooks.txt. See the diff bel
Am 17.04.2018 um 08:18 schrieb Eric Wong:
> Andreas Heiduk wrote:
>> Signed-off-by: Andreas Heiduk
>
> Thanks.
> Signed-off-by: Eric Wong
>
> And pushed for Junio:
[...]
I'd like to keep the patches together, so I borrow your 'Signed-off-By'
from the commit and do a complete reroll of this mi
Hello
In my search for a business partner i got your contact in google
search. My client is willing to invest $10 Million to $500
million but my client said he need a trusted partner who he can
have a meeting at the point of releasing his funds.
I told my client that you have a good profile w
On Wed, Apr 25, 2018 at 5:18 PM, Marc Branchaud wrote:
>> The best approach to do so is to have those people do the "touch"
>> thing in their own post-checkout hook. People who use Git as the
>> source control system won't have to pay runtime cost of doing the
>> touch thing, and we do not have t
This reroll incorporates the comments of the first version, including a
"large scale" rewrtie of githooks.txt. I'v added "Reviewed-by" and
"Signed-off-by" as appropriate.
Andreas Heiduk (6):
doc: improve formatting in githooks.txt
doc: align 'diff --no-index' in text with synopsis
doc: clari
The two '' parameters are not optional but the option
'--no-index' is. Also move the `--options` part to the same
place where the other variants show them.
All three items are already correct in the synopsis.
Signed-off-by: Andreas Heiduk
Reviewed-by: Martin Ågren
---
Documentation/git-diff.tx
Typeset commands and similar things with as `git foo` instead of
'git foo' or 'git-foo' and add linkgit to the commands which run
the hooks.
Signed-off-by: Andreas Heiduk
Reviewed-by: Martin Ågren
---
Documentation/githooks.txt | 115 +++--
1 file changed
Signed-off-by: Andreas Heiduk
Reviewed-by: Junio C Hamano
---
Documentation/revisions.txt | 6 ++
1 file changed, 6 insertions(+)
diff --git a/Documentation/revisions.txt b/Documentation/revisions.txt
index dfcc49c72c..c1d3a40a90 100644
--- a/Documentation/revisions.txt
+++ b/Documentation/
The subcommand 'commit-diff' does not support the option
'--add-author-from'.
Signed-off-by: Andreas Heiduk
Signed-off-by: Eric Wong
---
Documentation/git-svn.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/git-svn.txt b/Documentation/git-svn.txt
index d593
Explain that `git ls-files --ignored` requires at least one
of the `--exclude*` options to do its job.
Signed-off-by: Andreas Heiduk
---
Documentation/git-ls-files.txt | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/Documentation/git-ls-files.txt b/Documentation/git-ls-file
Add the missing `-o` shortcut for `--push-option` to the synopsis.
Add the missing `-d` shortcut for `--delete` in the main section.
Signed-off-by: Andreas Heiduk
Reviewed-by: Martin Ågren
---
Documentation/git-push.txt | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/Docum
Hi Johannes,
Thanks for your reply.
Part of my confusion was regarding the interaction between `-C` and
`--git-dir`. For instance, we have
$ git --git-dir target -C /tmp/tmp.Cl4aXMSVis init
Initialized empty Git repository in /tmp/tmp.Cl4aXMSVis/target/
which makes sense and is what I e
W dniu śro, 25.04.2018 o godzinie 11∶18 -0400, użytkownik Marc Branchaud
napisał:
> On 2018-04-25 04:48 AM, Junio C Hamano wrote:
> > "Robin H. Johnson" writes:
> >
> > > In the thread from 6 years ago, you asked about tar's behavior for
> > > mtimes. 'tar xf' restores mtimes from the tar archive
On 27 April 2018 at 19:04, Andreas Heiduk wrote:
> The two '' parameters are not optional but the option
> '--no-index' is. Also move the `--options` part to the same
> place where the other variants show them.
Should this commit message be updated after the changes you did to
address Junio's com
git format-patch is missing documentation for --relative.
There is also no auto complete(or tab complete, whatever it's called)
for the --relative switch/argument.
https://stackoverflow.com/a/16309416/222054
Thanks,
Kelly Elton
http://www.kellyelton.com
On Fri, Apr 27, 2018 at 1:04 PM, Andreas Heiduk wrote:
> The two '' parameters are not optional but the option
> '--no-index' is. Also move the `--options` part to the same
> place where the other variants show them.
>
> All three items are already correct in the synopsis.
>
> Signed-off-by: Andre
On Fri, Apr 27, 2018 at 1:04 PM, Andreas Heiduk wrote:
> Signed-off-by: Andreas Heiduk
> Reviewed-by: Junio C Hamano
> ---
> diff --git a/Documentation/revisions.txt b/Documentation/revisions.txt
> @@ -186,6 +190,8 @@ existing tag object.
> + Depending on the given text the shell's word splitti
https://git-scm.com/docs/git-apply#git-apply--pltngt
> -p
> Remove leading slashes from traditional diff paths. The default is 1.
This suggests to me the following outcomes:
1) home/user/repos/myrepo with -p1 becomes home/user/repos/myrepo
2) home/user/repos/myrepo with -p2 becomes home/user/re
Am 27.04.2018 um 19:18 schrieb Martin Ågren:
> On 27 April 2018 at 19:04, Andreas Heiduk wrote:
>> The two '' parameters are not optional but the option
>> '--no-index' is. Also move the `--options` part to the same
>> place where the other variants show them.
>
> Should this commit message be up
From: Elijah Newren
On Thu, Apr 26, 2018 at 5:54 PM, Ben Peart wrote:
> Can you write the documentation that clearly explains the exact behavior you
> want? That would kill two birds with one stone... :)
Sure, something like the following is what I envision, and I've tried to
include the sugg
On Fri, Apr 27, 2018 at 11:23:56AM +0900, Junio C Hamano wrote:
> I think demoting from copy to rename-only is a good idea, at least
> for now, because I do not believe we have figured out what we want
> to happen when we detect copied files are involved in a merge.
Does anyone know some threads c
Am 27.04.2018 um 19:33 schrieb Eric Sunshine:
> On Fri, Apr 27, 2018 at 1:04 PM, Andreas Heiduk wrote:
>> The two '' parameters are not optional but the option
>> '--no-index' is. Also move the `--options` part to the same
>> place where the other variants show them.
>>
>> All three items are alre
Am 27.04.2018 um 19:36 schrieb Eric Sunshine:
> On Fri, Apr 27, 2018 at 1:04 PM, Andreas Heiduk wrote:
>> Signed-off-by: Andreas Heiduk
>> Reviewed-by: Junio C Hamano
>> ---
>> diff --git a/Documentation/revisions.txt b/Documentation/revisions.txt
>> @@ -186,6 +190,8 @@ existing tag object.
>> +
On 27 April 2018 at 20:40, Andreas Heiduk wrote:
> Am 27.04.2018 um 19:33 schrieb Eric Sunshine:
>> On Fri, Apr 27, 2018 at 1:04 PM, Andreas Heiduk wrote:
>>> The two '' parameters are not optional but the option
>>> '--no-index' is. Also move the `--options` part to the same
>>> place where the
On 27 April 2018 at 20:28, Andreas Heiduk wrote:
> Am 27.04.2018 um 19:18 schrieb Martin Ågren:
>> On 27 April 2018 at 19:04, Andreas Heiduk wrote:
>>> The two '' parameters are not optional but the option
>>> '--no-index' is. Also move the `--options` part to the same
>>> place where the other v
On 27 April 2018 at 19:04, Andreas Heiduk wrote:
> Typeset commands and similar things with as `git foo` instead of
> 'git foo' or 'git-foo' and add linkgit to the commands which run
> the hooks.
>
> Signed-off-by: Andreas Heiduk
> Reviewed-by: Martin Ågren
Indeed. The difference between last t
When --prefix-tags is passed to `git remote add` the tagopt is set to
--prefix-tags and a second fetch line is added so tags are placed in
a separate hierarchy per remote.
For example:
$ git remote add -f --prefix-tags gbenchmark g...@github.com:google/benchmark
Updating gbenchmark
warning:
On Thu, Apr 26, 2018 at 4:24 PM, Junio C Hamano wrote:
> Junio C Hamano writes:
>
>
> Hence (1) we should detect and error out when --prefix-tags is used
> with mirror fetch near where we do the same for track used without
> mirror fetch already, (2) detect and error out when --prefix-tags is
> u
Am 27.04.2018 um 20:45 schrieb Martin Ågren:
> On 27 April 2018 at 20:28, Andreas Heiduk wrote:
>> Am 27.04.2018 um 19:18 schrieb Martin Ågren:
>>> On 27 April 2018 at 19:04, Andreas Heiduk wrote:
The two '' parameters are not optional but the option
'--no-index' is. Also move the `--op
On Fri, Apr 27, 2018 at 2:40 PM, Andreas Heiduk wrote:
> Am 27.04.2018 um 19:33 schrieb Eric Sunshine:
>> On Fri, Apr 27, 2018 at 1:04 PM, Andreas Heiduk wrote:
>>> @@ -13,7 +13,7 @@ SYNOPSIS
>>> -'git diff' [options] [--no-index] [--]
>>> +'git diff' [options] --no-index [--]
>>> @@ -29,7 +2
On Fri, Apr 27, 2018 at 12:08 PM, Wink Saville wrote:
>
> The other change was rather than using
> ""+refs/tags/*:refs/remote-tags/$name/*"
> I've changed it to "+refs/tags/*:refs/remote/tags/$name/*" which seems
> cleaner.
> Again, if remote-tags is preferred I'll change it back.
>From lookin
SYNOPSIS and other manuals use [options] but DESCRIPTION
used [--options].
Signed-off-by: Andreas Heiduk
---
Documentation/git-diff.txt | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/Documentation/git-diff.txt b/Documentation/git-diff.txt
index 6593b58299..7c2
On Tue, Apr 24, 2018 at 9:57 PM, Wink Saville wrote:
> If have a repository with a tag "v1.0.0" and I add a remote repository
> which also has a tag "v1.0.0" tag is overwritten.
I feel like this thread has gotten somewhat side-tracked by the valid
discussion about whether we should have remote tr
On Fri, Apr 27, 2018 at 7:18 PM, Michał Górny wrote:
> W dniu śro, 25.04.2018 o godzinie 11∶18 -0400, użytkownik Marc Branchaud
> napisał:
>> On 2018-04-25 04:48 AM, Junio C Hamano wrote:
>> > "Robin H. Johnson" writes:
>> >
>> > > In the thread from 6 years ago, you asked about tar's behavior fo
On Fri, Apr 27, 2018 at 11:37 AM, Eckhard Maaß
wrote:
> On Fri, Apr 27, 2018 at 11:23:56AM +0900, Junio C Hamano wrote:
>> I think demoting from copy to rename-only is a good idea, at least
>> for now, because I do not believe we have figured out what we want
>> to happen when we detect copied fil
During a series of fixup/squash commands, the interactive rebase builds
up a commit message with comments. This will be presented to the user in
the editor if at least one of those commands was a `squash`.
In any case, the commit message will be cleaned up eventually, removing
all those intermedia
When multiple fixup/squash commands are processed and the last one
causes merge conflicts and is skipped, we leave the "This is a
combination of ..." comments in the commit message.
Noticed by Eric Sunshine.
This regression test also demonstrates that we rely on the localized
version of
Eric Sunshine pointed out that I had such a commit message in
https://public-inbox.org/git/CAPig+cRrS0_nYJJY=o6cbov630snqhpv5qgrqdd8mw-syzn...@mail.gmail.com/
and I went on a hunt to figure out how the heck this happened.
Turns out that if there is a fixup/squash chain where the *last* command
fai
Previously, we only called run_git_commit() without EDIT_MSG when we also
passed in a default message.
However, an upcoming caller will want to commit without EDIT_MSG and
*without* a default message: to clean up fixup/squash comments in HEAD's
commit message.
Let's prepare for that.
Signed-off-
We previously relied on the localized versions of
# This is a combination of commits
(which we write into the commit messages during fixup/squash chains)
to contain encoded in ASCII.
This is not true in general, and certainly not true when compiled with
GETTEXT_POISON=TryToKillMe, as d
Hi Junio,
On Thu, 26 Apr 2018, Junio C Hamano wrote:
> Johannes Schindelin writes:
>
> > - if (export_object(&old_oid, type, raw, tmpfile))
> > - return -1;
> > - if (launch_editor(tmpfile, NULL, NULL) < 0)
> > - return error("editing object file failed");
> > - if (im
On 2018-04-27 01:03 PM, Duy Nguyen wrote:
On Wed, Apr 25, 2018 at 5:18 PM, Marc Branchaud wrote:
The best approach to do so is to have those people do the "touch"
thing in their own post-checkout hook. People who use Git as the
source control system won't have to pay runtime cost of doing the
On Fri, Apr 27, 2018 at 10:03 AM, Duy Nguyen wrote:
> On Wed, Apr 25, 2018 at 5:18 PM, Marc Branchaud wrote:
>>
>> * In a "file checkout" ("git checkout -- path/to/file"), $1 and $2 are
>> identical so the above loop does nothing. Offhand I'm not even sure how a
>> hook might get the right files
On Thu, Apr 26, 2018 at 05:46:28PM +0200, Duy Nguyen wrote:
> On Wed, Apr 25, 2018 at 8:49 PM, Martin Ågren wrote:
> > Once that is accomplished, I sort of suspect that this code will want to
> > be updated to not always blindly use the_hash_algo, but to always work
> > with SHA-1 sizes. Or rather
On Fri, Apr 27, 2018 at 1:48 PM, Johannes Schindelin
wrote:
> During a series of fixup/squash commands, the interactive rebase builds
> up a commit message with comments. This will be presented to the user in
> the editor if at least one of those commands was a `squash`.
This sounds as if the who
Hi Phillip,
On Sat, 21 Apr 2018, Phillip Wood wrote:
> On 20/04/18 13:18, Johannes Schindelin wrote:
> >
> > During a series of fixup/squash commands, the interactive rebase builds
> > up a commit message with comments. This will be presented to the user in
> > the editor if at least one of thos
It is fragile, as there is no way for the revision machinery to say "but
now I want to traverse the graph ignoring the graft file" e.g. when
pushing commits to a remote repository (which, as a consequence, can
miss commits).
And we already have a better solution with `git replace --graft
[...]`.
The proof, as the saying goes, lies in the pudding. So here is a
regression test that not only demonstrates what the option is supposed to
accomplish, but also demonstrates that it does accomplish it.
Signed-off-by: Johannes Schindelin
---
t/t6050-replace.sh | 20
1 file cha
We have the BUG() macro for that purpose.
Signed-off-by: Johannes Schindelin
---
builtin/replace.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/builtin/replace.c b/builtin/replace.c
index 245d3f4164e..e345a5a0f1c 100644
--- a/builtin/replace.c
+++ b/builtin/replace.c
@@ -5
This option is intended to help with the transition away from the
now-deprecated graft file.
Signed-off-by: Johannes Schindelin
---
Documentation/git-replace.txt | 11 ++---
builtin/replace.c | 44 ++-
2 files changed, 51 insertions(+), 4 deletions
This is a simple function that will interpret a string as a whitespace
delimited list of values, and add those values into the array.
Note: this function does not (yet) offer to split by arbitrary delimiters,
or keep empty values in case of runs of whitespace, or de-quote Unix shell
style. All fo
This is yet another patch to be filed under the keyword "libification".
There is one subtle change in behavior here, where a `git log` that has
been asked to show the mergetags would now stop reporting the mergetags
upon the first failure, whereas previously, it would have continued to the
next me
File this away as yet another patch in the "libification" category.
As with all useful functions, in the next commit we want to use
create_graft() from a higher-level function where it would be
inconvenient if the called function simply die()s: if there is a
problem, we want to let the user know h
The grafts feature was a convenient way to "stitch together" ancient
history to the fresh start of linux.git.
Its implementation is, however, not up to Git's standards, as there are
too many ways where it can lead to surprising and unwelcome behavior.
For example, when pushing from a repository w
The graft file is deprecated now, so let's use replace refs in the example
in filter-branch's man page instead.
Suggested-by: Eric Sunshine
Signed-off-by: Johannes Schindelin
---
Documentation/git-filter-branch.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentatio
Now that grafts are deprecated, we should start to assume that readers
have no idea what grafts are. So it makes more sense to make the
description of the "shallow" feature stand on its own.
Suggested-by: Eric Sunshine
Helped-by: Junio Hamano
Signed-off-by: Johannes Schindelin
---
Documentatio
The functionality is now implemented as `git replace
--convert-graft-file`.
Signed-off-by: Johannes Schindelin
---
contrib/convert-grafts-to-replace-refs.sh | 28 ---
1 file changed, 28 deletions(-)
delete mode 100755 contrib/convert-grafts-to-replace-refs.sh
diff --git a/c
It is tempting to do away with commit_graft altogether (in the long
haul), now that grafts are deprecated.
However, the shallow feature needs a couple of things that the replace
refs cannot fulfill. Let's point that out in the documentation.
Signed-off-by: Johannes Schindelin
---
Documentation/
On 2018-04-26 19:23, Elijah Newren wrote:
On Thu, Apr 26, 2018 at 10:13 AM, Torsten Bögershausen wrote:
Hm,
thanks for the report.
I don't have a high sierra box, but I can probably get one.
t0050 -should- pass automagically, so I feel that I can do something.
Unless someone is faster of cour
When I reimplemented the most performance-critical bits of the
interactive rebase in the sequencer, to speed up `git rebase -i`
particularly on Windows (even if the benefits are still quite notable on
Linux or macOS), I punted on the --root part.
I had always hoped that some other contributor (or
When an interactive rebase wants to recreate a root commit, it
- first creates a new, empty root commit,
- checks it out,
- converts the next `pick` command so that it amends the empty root
commit
Introduce support in the sequencer to handle such an empty root commit,
by looking for the file /re
This patch extracts the code from is_index_unchanged() to initialize or
update the index' cache tree (i.e. a tree object reflecting the current
index' top-level tree).
The new helper will be used in the upcoming code to support `git rebase
-i --root` via the sequencer.
Signed-off-by: Johannes Sch
In the context of the new --rebase-merges mode, which was designed
specifically to allow for changing the existing branch topology
liberally, a user may want to extract commits into a completely fresh
branch that starts with a newly-created root commit.
This is now possible by inserting the comman
In this developer's earlier attempt to accelerate interactive rebases by
converting large parts from Unix shell script into portable, performant
C, the --root handling was specifically excluded (to simplify the task a
little bit; it still took over a year to get that reduced set of patches
into Git
Reported by Wink Saville: when rebasing with no-rebase-cousins, we
will want to refrain from rebasing all of them, even when they are
root commits.
Signed-off-by: Johannes Schindelin
---
sequencer.c | 3 ++-
t/t3430-rebase-merges.sh | 25 +
2 files changed,
When a user provides a todo list containing something like
reset [new root]
merge my-branch
let's do the same as if pulling into an orphan branch: simply
fast-forward.
Signed-off-by: Johannes Schindelin
---
sequencer.c | 12
t/t3430-rebase-merges.sh |
Hi,
On Fri, Apr 27, 2018 at 3:37 AM, Middelschulte, Leif
wrote:
> Am Donnerstag, den 26.04.2018, 17:19 -0700 schrieb Elijah Newren:
>> On Thu, Apr 26, 2018 at 3:49 AM, Middelschulte, Leif
>> wrote:
>> > Problem case: Merge either branch into the other
>> >
>> > Expected behavior: Merge conflict
Hi,
I discovered that I was able to delete the feature branch I was in, due to some
fat fingering on my part and case insensitivity. I never realized this could
be done before. A quick google search did not give me a whole lot to work
with...
Steps to reproduce:
1. Create a feature branch,
Hallo Johannes,
> diff --git a/t/t6050-replace.sh b/t/t6050-replace.sh
> index c630aba657e..bed86a0af3d 100755
> --- a/t/t6050-replace.sh
> +++ b/t/t6050-replace.sh
> @@ -444,4 +444,24 @@ test_expect_success GPG '--graft on a commit with a
> mergetag' '
Note the GPG prereq of the previous test.
On Fri, Apr 27, 2018 at 11:08 PM, brian m. carlson
wrote:
> On Thu, Apr 26, 2018 at 05:46:28PM +0200, Duy Nguyen wrote:
>> On Wed, Apr 25, 2018 at 8:49 PM, Martin Ågren wrote:
>> > Once that is accomplished, I sort of suspect that this code will want to
>> > be updated to not always blindly use t
On Fri, Apr 27, 2018 at 11:08 PM, Elijah Newren wrote:
> On Fri, Apr 27, 2018 at 10:03 AM, Duy Nguyen wrote:
>> On Wed, Apr 25, 2018 at 5:18 PM, Marc Branchaud wrote:
>>>
>>> * In a "file checkout" ("git checkout -- path/to/file"), $1 and $2 are
>>> identical so the above loop does nothing. Off
On Fri, Apr 27, 2018 at 11:08 PM, Marc Branchaud wrote:
>> On Wed, Apr 25, 2018 at 5:18 PM, Marc Branchaud
>> This is a limitation of the current post-checkout hook. $3==0 from the
>> hook lets us know this is not a branch switch, but it does not really
>> tell you the affected paths. If it someh
SZEDER Gábor writes:
> The commit pointed to by the tag Pacemaker-0.6.1 and its parent have a
> serious clock skew, i.e. they are a few months older than their parents:
> [...]
> (branch|tag|describe|...) (--contains|--merged) use the commit timestamp
> information as a heuristic to avoid travers
85 matches
Mail list logo
