Junio C Hamano writes:
> Coming back to the command line syntax for the new feature, if I had
> to choose, I would say
>
> git diff --no-index [-] [--]
>
> perhaps? As we never compare anything other than two things,...
Actually, I am not so sure about this anymore.
It is not entirely
On Fri, Sep 19, 2014 at 5:41 AM, Junio C Hamano wrote:
>> @@ -194,19 +207,23 @@ void diff_no_index(struct rev_info *revs,
>> int j;
>> if (!strcmp(argv[i], "--no-index"))
>> i++;
>> - else if (!strcmp(argv[i], "--"))
>> + el
This patch fixes two problems with using :(glob) (or even "*.c"
without ":(glob)").
The first one is we forgot to turn on the 'recursive' flag in struct
pathspec. Without that, tree_entry_interesting() will not mark
potential directories "interesting" so that it can confirm whether
those directori
On Sat, Sep 20, 2014 at 10:41 PM, Duy Nguyen wrote:
> On Thu, Sep 11, 2014 at 11:02:36AM -0400, Marc Branchaud wrote:
>> Um, didn't you say in [1] that you'd use the text I posted in [2]?
>>
>> [1] http://article.gmane.org/gmane.comp.version-control.git/256446
>> [2] http://article.gmane.org/gmane
On Sat, Sep 20, 2014 at 10:54 PM, Duy Nguyen wrote:
> On Fri, Sep 12, 2014 at 10:06 AM, Eric Sunshine
> wrote:
>> One minor addition for clarification would be to mention that the 'git
>> prune --worktrees' invocation applies to the main worktree:
>>
>> When you are done with a linked workin
Although the "git notes" man page advertises that we support binary-safe
notes addition with the -C option, we currently do not support adding the
empty note (i.e. using the empty blob to annotate an object). Instead,
an empty note is always treated as an intent to remove the note
altogether.
Intr
On Fri, Sep 12, 2014 at 10:06 AM, Eric Sunshine wrote:
> One minor addition for clarification would be to mention that the 'git
> prune --worktrees' invocation applies to the main worktree:
>
> When you are done with a linked working tree, you can simply delete
> it. You can clean up any s
On Thu, Sep 11, 2014 at 11:02:36AM -0400, Marc Branchaud wrote:
> Um, didn't you say in [1] that you'd use the text I posted in [2]?
>
> [1] http://article.gmane.org/gmane.comp.version-control.git/256446
> [2] http://article.gmane.org/gmane.comp.version-control.git/256323
That's the problem with
On Sat, Sep 20, 2014 at 9:47 PM, James H. Fisher wrote:
> In the documentation for git notes [1] I read:
>
> In principle, a note is a regular Git blob, and any kind of
> (non-)format is accepted.
>
> Then, since the empty string is a valid regular Git blob, the empty
> string is also a va
Apologies for re-sending; unclear whether my email was delivered since I sent
it before my subscription was confirmed.
On 20 Sep 2014, at 20:47, James H. Fisher wrote:
> In the documentation for git notes [1] I read:
>
>In principle, a note is a regular Git blob, and any kind of (non-)form
Am 20.09.2014 um 20:29 schrieb René Scharfe:
Deduplicate code common to both branches of if statements.
There is no 2/2, this patch is the only one at this time.
René
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More
In the documentation for git notes [1] I read:
In principle, a note is a regular Git blob, and any kind of (non-)format is
accepted.
Then, since the empty string is a valid regular Git blob, the empty string is
also a valid git note.
Therefore this behavior was unexpected for me:
> gi
Deduplicate code common to both branches of if statements.
Signed-off-by: Rene Scharfe
---
graph.c | 17 -
1 file changed, 4 insertions(+), 13 deletions(-)
diff --git a/graph.c b/graph.c
index dfb99f6..52605e4 100644
--- a/graph.c
+++ b/graph.c
@@ -1161,20 +1161,11 @@ static voi
Stepan Kasal writes:
> diff --git a/t/t7004-tag.sh b/t/t7004-tag.sh
> index 143a8ea..a911df0 100755
> --- a/t/t7004-tag.sh
> +++ b/t/t7004-tag.sh
> @@ -1423,4 +1423,30 @@ EOF
> test_cmp expect actual
> '
>
> +run_with_limited_stack () {
> + (ulimit -s 64 && "$@")
> +}
That is way to
After staging the removal of a submodule, diff-index does not consider this
when "--ignore-submodules" is being used:
# In a repository with submodule "sm":
% git rm --cached sm
% git diff-index --cached --quiet --ignore-submodules HEAD
% echo $?
0
% git status
On bran
Changes all Email to E-Mail, as this is the correct form in german.
Phillip
Signed-off-by: Phillip Sz
---
po/de.po | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/po/de.po b/po/de.po
index e5d2b25..c6aa69f 100644
--- a/po/de.po
+++ b/po/de.po
@@ -2691,7 +2691,
Sitaram
Looks good and can be very useful. I can even image some edge cases of
using this in automation. Will have to find the time to test this.
On Sat, Sep 20, 2014 at 8:50 AM, Sitaram Chamarty wrote:
> Hi all,
>
> I've just created a general purpose TOTP "gatekeeper" that is designed
> to gat
Hi all,
I've just created a general purpose TOTP "gatekeeper" that is designed
to gate access to any service on any server/OS (as long as traffic can
only go *through* the TOTP gatekeeper).
The inspiration was Konstantin Ryabitsev's implementation of two-factor
authentication for kernel.org -- fr
Read the configuration to get trailer information, and then process
it and store it in a doubly linked list.
The config information is stored in the list whose first item is
pointed to by:
static struct trailer_item *first_conf_item;
Signed-off-by: Christian Couder
Signed-off-by: Junio C Hamano
Read trailers from a file or from stdin, parse the trailers and then
put the result into a doubly linked list.
Signed-off-by: Christian Couder
Signed-off-by: Junio C Hamano
---
trailer.c | 123 ++
1 file changed, 123 insertions(+)
dif
Signed-off-by: Christian Couder
Signed-off-by: Junio C Hamano
---
t/t7513-interpret-trailers.sh | 726 ++
1 file changed, 726 insertions(+)
create mode 100755 t/t7513-interpret-trailers.sh
diff --git a/t/t7513-interpret-trailers.sh b/t/t7513-interpret-tr
Let the user specify a command that will give on its standard output
the value to use for the specified trailer.
Signed-off-by: Christian Couder
Signed-off-by: Junio C Hamano
---
trailer.c | 85 ++-
1 file changed, 84 insertions(+), 1
Implement the logic to process trailers from the input message
and from arguments.
At the beginning trailers from the input message are in their
own "in_tok" doubly linked list, and trailers from arguments
are in their own "arg_tok" doubly linked list.
The lists are traversed and when an "arg_tok
This patch adds the process_trailers() function that
calls all the previously added processing functions
and then prints the results on the standard output.
Signed-off-by: Christian Couder
Signed-off-by: Junio C Hamano
---
trailer.c | 81 +
While at it add git-interpret-trailers to "command-list.txt".
Signed-off-by: Christian Couder
Signed-off-by: Junio C Hamano
---
Documentation/git-interpret-trailers.txt | 313 +++
command-list.txt | 1 +
2 files changed, 314 insertions(+)
c
We will use a doubly linked list to store all information
about trailers and their configuration.
This way we can easily remove or add trailers to or from
trailer lists while traversing the lists in either direction.
Signed-off-by: Christian Couder
Signed-off-by: Junio C Hamano
---
Makefile |
This patch series implements a new command:
git interpret-trailers
and an infrastructure to process trailers that can be reused,
for example in "commit.c".
1) Rationale
This command should help with RFC 822 style headers, called
"trailers", that are found at the end of commit messages.
Parse the trailer command line arguments and put
the result into an arg_tok doubly linked list.
Signed-off-by: Christian Couder
Signed-off-by: Junio C Hamano
---
trailer.c | 125 ++
1 file changed, 125 insertions(+)
diff --git a/trail
And add a few other tests for some special cases.
Signed-off-by: Christian Couder
Signed-off-by: Junio C Hamano
---
t/t7513-interpret-trailers.sh | 125 ++
1 file changed, 125 insertions(+)
diff --git a/t/t7513-interpret-trailers.sh b/t/t7513-interpret-t
This patch adds the "git interpret-trailers" command.
This command uses the previously added process_trailers()
function in trailer.c.
Signed-off-by: Christian Couder
Signed-off-by: Junio C Hamano
---
.gitignore | 1 +
Makefile | 1 +
builtin.h
Am 18.09.2014 um 18:57 schrieb Patrick Reynolds:
> Blocked and ignored signals -- but not caught signals -- are inherited
> across exec. Some callers with sloppy signal-handling behavior can call
> git with SIGPIPE blocked or ignored, even non-deterministically. When
> SIGPIPE is blocked or ignor
31 matches
Mail list logo
