I see, it makes sense ;-) Indeed it would seem logical to have all
commands showing diffs (diff, add -p, log -p, reset -p, etc..) respect
the diff options.
Thanks for your quick answer!
2016-06-14 23:45 GMT+02:00 Junio C Hamano :
> Jeff King writes:
>
>> Nobody noticed so far because originally
Add example usage to the git-svn documentation.
Reported-by: Joseph Pecoraro
Signed-off-by: Alfred Perlstein
---
Junio, Pranit, + all,
A week ago I was requested to provide documentation for the
'svn propset' command. I have attached a diff off of the
'maint' branch for this, however it seem
On Wed, Jun 15, 2016 at 12:27:15PM +0800, ZhenTian wrote:
> I got two more lines from gpg -v during commit with -S:
> ```
> gpg: writing to stdout
> gpg: RSA/SHA1 signature from: "2EF2AD6E Tian Zhen "
> ```
>
> after I commit, I push it to remote, but someone had pushed before to
> master branch,
Hi Michael and Peff,
I got two more lines from gpg -v during commit with -S:
```
gpg: writing to stdout
gpg: RSA/SHA1 signature from: "2EF2AD6E Tian Zhen "
```
after I commit, I push it to remote, but someone had pushed before to
master branch, so I pull on master branch(`git pull --rebase`), the
On Tue, Jun 14, 2016 at 05:36:35PM +0700, Duy Nguyen wrote:
> > or what would happen if the packfile
> > fetch failed (we'd already have deleted the old refs, but wouldn't fetch
> > the new ones).
>
> Off topic, but this sounds like a bug to me. We could have kept ref
> update more consistent (ma
On Tue, Jun 14, 2016 at 02:25:42PM -0700, Junio C Hamano wrote:
> > Also, reorganize the overall control flow, remove some superfluous
> > variables and replace a custom implementation of strpbrk() with a call
> > to the standard C library function.
>
> I find that calling the loop "a custom impl
On Tue, Jun 14, 2016 at 06:26:33PM -0400, Jeff King wrote:
> > > > bottom = signature->len;
> > > > - len = strbuf_read(signature, gpg.out, 1024);
> > > > + strbuf_read(signature, gpg.out, 1024);
> > > > + strbuf_read(&err, gpg.err, 0);
> > >
> > > H, isn't this aski
On Tue, Jun 14, 2016 at 03:08:04PM -0700, Junio C Hamano wrote:
> Here are the topics that have been cooking. Commits prefixed with
> '-' are only in 'pu' (proposed updates) while commits prefixed with
> '+' are in 'next'. The ones marked with '.' do not appear in any of
> the integration branche
On Tue, Jun 14, 2016 at 04:47:35PM -0700, Junio C Hamano wrote:
> Jeff King writes:
>
> > I'm still undecided on whether it is a better approach than making
> > sure the stdout we got looks sane. In particular I'd worry that it
> > would make things harder for somebody trying to plug in somethin
Jeff King writes:
> I'm still undecided on whether it is a better approach than making
> sure the stdout we got looks sane. In particular I'd worry that it
> would make things harder for somebody trying to plug in something
> gpg-like (e.g., if you wanted to do something exotic like call a
> prog
On 06/09/2016 01:49 PM, Matthieu Moy wrote:
Samuel GROOT writes:
If used with `in-reply-to=`, cite the message body of the given
email file. Otherwise, do nothing.
It should at least warn when --in-reply-to= is not given
(either no --in-reply-to or --in-reply-to=). I don't see any
use-case w
On 06/09/2016 11:45 AM, Matthieu Moy wrote:
Samuel GROOT writes:
diff --git a/Documentation/git-send-email.txt b/Documentation/git-send-email.txt
index edbba3a..21776f0 100644
--- a/Documentation/git-send-email.txt
+++ b/Documentation/git-send-email.txt
@@ -84,13 +84,16 @@ See the CONFIGURAT
On 06/08/2016 08:23 PM, Junio C Hamano wrote:
Samuel GROOT writes:
+if ($initial_reply_to && -f $initial_reply_to) {
+ my $error = validate_patch($initial_reply_to);
This call is wrong, isn't it?
You are not going to send out the message you are responding to (the
message may not even
On Tue, Jun 14, 2016 at 05:50:19PM -0400, Jeff King wrote:
> On Tue, Jun 14, 2016 at 11:13:54AM -0700, Junio C Hamano wrote:
>
> > Michael J Gruber writes:
> >
> > > bottom = signature->len;
> > > - len = strbuf_read(signature, gpg.out, 1024);
> > > + strbuf_read(signature, gpg.out, 1024);
>
On 06/14/2016 12:47 AM, Eric Wong wrote:
Samuel GROOT wrote:
On 06/09/2016 02:21 AM, Eric Wong wrote:
Samuel GROOT wrote:
Email::Simple library uses qr/\x0a\x0d|\x0d\x0a|\x0a|\x0d/ [1].
Should we handle \n\r at end of line as well?
"\n\r" can never happen with local $/ = "\n"
If the emai
Here are the topics that have been cooking. Commits prefixed with
'-' are only in 'pu' (proposed updates) while commits prefixed with
'+' are in 'next'. The ones marked with '.' do not appear in any of
the integration branches, but I am still holding onto them.
Git 2.9 has been tagged. Let's wa
Jeff King writes:
> Yeah, I don't think it has kept up with our work. My statement above was
> "I don't think we'd _ever_ want to consider sharness the upstream, even
> if it were up to date", but obviously there would be a lot of work to
> even get it there.
I actually was a lot more optimistic
On Tue, Jun 14, 2016 at 11:13:54AM -0700, Junio C Hamano wrote:
> Michael J Gruber writes:
>
> > bottom = signature->len;
> > - len = strbuf_read(signature, gpg.out, 1024);
> > + strbuf_read(signature, gpg.out, 1024);
> > + strbuf_read(&err, gpg.err, 0);
>
> H, isn't this asking f
On Tue, Jun 14, 2016 at 02:43:19PM -0700, Junio C Hamano wrote:
> Jeff King writes:
>
> > I don't think the Git project would ever want to say "sharness is the
> > upstream, and we are now just a user of it". But I wonder if we could
> > break down test-lib.sh to keep the Git-specific parts sepa
Jeff King writes:
> Nobody noticed so far because originally the compaction heuristic was on
> by default, and so just worked everywhere. But we backed off on that at
> the last minute after finding a few cases where the diff looks worse.
Yup, and that is why this is called "experimental" in the
Jeff King writes:
> I don't think the Git project would ever want to say "sharness is the
> upstream, and we are now just a user of it". But I wonder if we could
> break down test-lib.sh to keep the Git-specific parts separate, which
> would make it easier for sharness to pull the other bits as a
On Tue, Jun 14, 2016 at 04:22:54PM +0200, Alex Prengère wrote:
> Hello,
> I just did a fresh clone of git from Github and installed the version
> 2.9.0 on Fedora 22.
>
> I tried the new compactionHeuristic = true, which is awesome.
> The only thing that struck me was that this option was not used
On Tue, 14 Jun 2016 10:06:16 +, Junio C Hamano wrote:
...
>
> IIRC, untracked files are kept during merge and across checking out
> another branch. Files that are deliberately marked as ignored by
> listing them to .gitignore mechanism are considered expendable, and
> they will be removed as
On Tue, Jun 14, 2016 at 09:34:17PM +0200, Christian Couder wrote:
> Version 1.0.0 of Sharness [1] -- the test harness library derived from
> Git's test lib -- is released.
Cool. Git's test harness is something I really miss having in other
projects. I'm glad this project exists. :)
> This releas
Lukas Fleischer writes:
Lukas Fleischer writes:
> Improve the readability of recv_sideband() significantly by replacing
s/significantly //; "making it readable" is already a subjective
goodness criterion, and you do not have to make it sound even more
subjective. Let the updated result convin
On Tue, Jun 14, 2016 at 01:28:39PM -0700, Junio C Hamano wrote:
> These callers appear to expect that deref_tag() is to peel one layer
> of a tag, but the function does not work that way; it has its own
> loop to unwrap tags until an object that is not a tag appears.
Looks obviously correct.
-Pe
On Tue, Jun 14, 2016 at 9:48 PM, Stefan Beller wrote:
> On Tue, Jun 14, 2016 at 12:34 PM, Christian Couder
> wrote:
>>
>> Sharness was first announced on this list in July 2012 [4]. It was
>> created from Git's test lib in April 2011 by Mathias Lafeldt who
>> improved and maintained it until a fe
On Tue, 14 Jun 2016 at 23:00:38, Lukas Fleischer wrote:
> Improve the readability of recv_sideband() significantly by replacing
> fragile buffer manipulations with string buffers and more sophisticated
> format strings. Note that each line is printed using a single write()
> syscall to avoid garble
Improve the readability of recv_sideband() significantly by replacing
fragile buffer manipulations with string buffers and more sophisticated
format strings. Note that each line is printed using a single write()
syscall to avoid garbled output when multiple processes write to stderr
in parallel, se
These callers appear to expect that deref_tag() is to peel one layer
of a tag, but the function does not work that way; it has its own
loop to unwrap tags until an object that is not a tag appears.
Signed-off-by: Junio C Hamano
---
builtin/blame.c | 6 ++
line-log.c | 3 +--
2 files cha
On Tue, 14 Jun 2016, Lukas Fleischer wrote:
> On Tue, 14 Jun 2016 at 19:55:06, Nicolas Pitre wrote:
> > It is not buffered as it writes to stderr. And some C libs do separate
> > calls to write() for every string format specifier. So "%s%s%c" may end
> > up calling write() 3 times depending on t
On Tue, Jun 14, 2016 at 12:34 PM, Christian Couder
wrote:
> Hi,
>
> Version 1.0.0 of Sharness [1] -- the test harness library derived from
> Git's test lib -- is released.
>
> This release contains many upstream fixes and improvements from Git
> and a lot of specific user contributed features [2].
Hi,
Version 1.0.0 of Sharness [1] -- the test harness library derived from
Git's test lib -- is released.
This release contains many upstream fixes and improvements from Git
and a lot of specific user contributed features [2].
It's the first release since v0.3.0 in April 2013 [3].
Sharness was
Lukas Fleischer writes:
> One possible solution is using strbuf and constructing the message as we
> did before. However, that still relies on fprintf() only calling write()
> once per format specifier. While that is probably true for all existing
> implementations, I don't think it is guaranteed
On Tue, 14 Jun 2016 at 20:11:12, Junio C Hamano wrote:
> Nicolas Pitre writes:
>
> > It is not buffered as it writes to stderr. And some C libs do separate
> > calls to write() for every string format specifier. So "%s%s%c" may end
> > up calling write() 3 times depending on the implementation.
Keith McGuigan writes:
> Yeah that was the only place I found where it was doing the strdup
> already (and in that situation, it has to). All the other places just
> grabbed remote->name.
>
> Yes, sorry, I can sign off on this. Do you want me to resend with the
> header in place, or is this con
Yeah that was the only place I found where it was doing the strdup
already (and in that situation, it has to). All the other places just
grabbed remote->name.
Yes, sorry, I can sign off on this. Do you want me to resend with the
header in place, or is this confirmation good enough?
--
- Keith
kmcgui...@twopensource.com writes:
> From: Keith McGuigan
>
> Make fetch's string_list of remote names owns all of its string items
> (strdup'ing when necessary) so that it can deallocate them safely when
> clearing.
>
> ---
OK.
When I pointed out the call to string_list_append() in
get_remote_
Instead of always requiring both ends of a range, we could DWIM
"OLD", which could be a misspelt "OLD..", to be a range that ends at
the current commit.
Signed-off-by: Junio C Hamano
---
* I am not convinced that this is a good change, though. It is
true that there is no other sensible inte
From: Keith McGuigan
Make fetch's string_list of remote names owns all of its string items
(strdup'ing when necessary) so that it can deallocate them safely when
clearing.
---
builtin/fetch.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/builtin/fetch.c b/builtin/fet
Michael J Gruber writes:
> bottom = signature->len;
> - len = strbuf_read(signature, gpg.out, 1024);
> + strbuf_read(signature, gpg.out, 1024);
> + strbuf_read(&err, gpg.err, 0);
H, isn't this asking for a deadlock? When GPG spews more than
what would fit in a pipe buffer
Nicolas Pitre writes:
> It is not buffered as it writes to stderr. And some C libs do separate
> calls to write() for every string format specifier. So "%s%s%c" may end
> up calling write() 3 times depending on the implementation. The example
> I gave in commit ed1902ef5c is real and I even o
On Tue, 14 Jun 2016, Lukas Fleischer wrote:
> Hi Nicolas,
>
> On Tue, 14 Jun 2016 at 19:09:15, Nicolas Pitre wrote:
> > I just looked again at all the contraptions _I_ wrote (not Junio's) for
> > a reason why I went to such extremes in making this code co complicated.
> >
> > One aspect that is
Keith McGuigan writes:
> As an alternative, I could xstrdup each instance where remote->name is
> appended,
> which would make the string_list a homogenous dup'd list, which we
> could then free.
Yeah, I think that is the right way to fix it, even though I agree
with you that a small leak you i
Christian Couder writes:
>> Before this patch, the program said "fatal: $message" and exited
>> with status = 128. All these changes in this step modifies the
>> external behaviour and make it say "error: $message" and exit with
>> status = 1 (at least the caller in apply_all_patches() does so).
"git blame --reverse OLD..NEW -- PATH" tells us to start from the
contents in PATH at OLD and observe how each line is changed while
the history developers up to NEW, and report for each line the
latest commit up to which the line survives in the original form.
If you say "git blame --reverse NEW
"git blame --reverse OLD..NEW -- PATH" tells us to start from the
contents in PATH at OLD and observe how each line is changed while
the history developers up to NEW, and report for each line the
latest commit up to which the line survives in the original form.
If you say "git blame --reverse NEW
On Tue, 14 Jun 2016 17:49:50 +0100
Maria Jose Fernandez wrote:
> I am very sorry but I am not understanding what you are saying.
> I will try with homebrew and see if it works that way.
Torstean means:
1. Using the Finder, locate the Terminal application and run it.
An open with command pro
On Mon, 13 Jun 2016, Nicolas Pitre wrote:
> On Mon, 13 Jun 2016, Lukas Fleischer wrote:
>
> > Improve the readability of recv_sideband() significantly by replacing
> > fragile buffer manipulations with more sophisticated format strings.
> > Also, reorganize the overall control flow, remove some s
Andreas Krey writes:
> when I have an ignored file in my workspace, is git
> then also assumed not to remove it in the course
> of a merge?
IIRC, untracked files are kept during merge and across checking out
another branch. Files that are deliberately marked as ignored by
listing them to .gitig
I am very sorry but I am not understanding what you are saying.
I will try with homebrew and see if it works that way.
> On 14 Jun 2016, at 17:48, Torsten Bögershausen wrote:
>
> On 14.06.16 18:45, Maria Jose Fernandez wrote:
>> From http://git-scm.com/download/mac I clicked to download manuall
On 14.06.16 18:45, Maria Jose Fernandez wrote:
> From http://git-scm.com/download/mac I clicked to download manually.
> Then it goes to
> https://sourceforge.net/projects/git-osx-installer/files/git-2.8.1-intel-universal-mavericks.dmg/download?use_mirror=autoselect
> I found the git - 2.8.1-intel-
On Tue, 14 Jun 2016, Johannes Schindelin wrote:
> Hi Nico,
>
> On Tue, 14 Jun 2016, Nicolas Pitre wrote:
>
> > On Tue, 14 Jun 2016, Johannes Schindelin wrote:
> >
> > > On Mon, 13 Jun 2016, Nicolas Pitre wrote:
> > >
> > > > On Mon, 13 Jun 2016, Lukas Fleischer wrote:
> > > >
> > > > > Improv
Hi all,
when I have an ignored file in my workspace, is git
then also assumed not to remove it in the course
of a merge?
Shouldn't it then say that the file is ignored,
as it does not show up in the untracked section
of git status?
Regards, Andreas
PS: Test script (will remove anything named 't
On 14.06.16 18:06, Konstantin Khomoutov wrote:
> On Tue, 14 Jun 2016 16:56:15 +0100
> Maria Jose Fernandez wrote:
>
>> I am doing a data science course and need to download GIT but for
>> some reason I can’t installed it. I called Apple but they couldn’t
>> help and suggested me to contact you gu
On Tue, 14 Jun 2016 16:56:15 +0100
Maria Jose Fernandez wrote:
> I am doing a data science course and need to download GIT but for
> some reason I can’t installed it. I called Apple but they couldn’t
> help and suggested me to contact you guys.
So you proceeded to http://git-scm.com/download/mac
Hello,
I am doing a data science course and need to download GIT but for some reason I
can’t installed it. I called Apple but they couldn’t help and suggested me to
contact you guys.
I hope you can help me.
Thank you very much,
Maria Jose Freeman--
To unsubscribe from this list: send the line
Hi Nico,
On Tue, 14 Jun 2016, Nicolas Pitre wrote:
> On Tue, 14 Jun 2016, Johannes Schindelin wrote:
>
> > On Mon, 13 Jun 2016, Nicolas Pitre wrote:
> >
> > > On Mon, 13 Jun 2016, Lukas Fleischer wrote:
> > >
> > > > Improve the readability of recv_sideband() significantly by
> > > > replacing
On Tue, 14 Jun 2016, Johannes Schindelin wrote:
> Hi,
>
> On Mon, 13 Jun 2016, Nicolas Pitre wrote:
>
> > On Mon, 13 Jun 2016, Lukas Fleischer wrote:
> >
> > > Improve the readability of recv_sideband() significantly by replacing
> > > fragile buffer manipulations with more sophisticated format
When we create a signature, it may happen that gpg returns with
"success" but not with an actual detached signature on stdout.
Check for the correct signature creation status to catch these cases
better. Really, --status-fd parsing is the only way to check gpg status
reliably. We do the same for v
The send_sideband() function uses write_or_die() for writing data which
immediately terminates the process on errors. If no such error occurred,
send_sideband() always returned the value that was passed as fourth
parameter prior to this commit. This value is already known to the
caller in any case,
The send_client_data() function uses write_or_die() for writing data
which immediately terminates the process on errors. If no such error
occurred, send_client_data() always returned the value that was passed
as third parameter prior to this commit. This value is already known to
the caller in any
Hello,
I just did a fresh clone of git from Github and installed the version
2.9.0 on Fedora 22.
I tried the new compactionHeuristic = true, which is awesome.
The only thing that struck me was that this option was not used when
doing an interactive staging, meaning `git diff` and `git add -p` will
Hi,
On Mon, 13 Jun 2016, Nicolas Pitre wrote:
> On Mon, 13 Jun 2016, Lukas Fleischer wrote:
>
> > Improve the readability of recv_sideband() significantly by replacing
> > fragile buffer manipulations with more sophisticated format strings.
> > Also, reorganize the overall control flow, remove s
When we create a signature, it may happen that gpg returns with
"success" but not with an actual detached signature on stdout.
Check for the correct header to catch these cases better. We use the
same parse_signature function for that that we use otherwise, so that
gpg specifics are localised ther
Michael J Gruber venit, vidit, dixit 14.06.2016 13:34:
> Jeff King venit, vidit, dixit 14.06.2016 13:20:
>> On Tue, Jun 14, 2016 at 01:11:19PM +0200, Michael J Gruber wrote:
>>
>>> When we create a signature, it may happen that gpg returns with
>>> "success" but not with an actual detached signatur
Helpful if your pkg-config executable has a prefix based on the
architecture, for example.
Signed-off-by: Heiko Becker
---
contrib/credential/gnome-keyring/Makefile | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/contrib/credential/gnome-keyring/Makefile
b/contrib/crede
Jeff King venit, vidit, dixit 14.06.2016 13:20:
> On Tue, Jun 14, 2016 at 01:11:19PM +0200, Michael J Gruber wrote:
>
>> When we create a signature, it may happen that gpg returns with
>> "success" but not with an actual detached signature on stdout.
>>
>> Check for the correct header to catch the
On Tue, Jun 14, 2016 at 01:11:19PM +0200, Michael J Gruber wrote:
> When we create a signature, it may happen that gpg returns with
> "success" but not with an actual detached signature on stdout.
>
> Check for the correct header to catch these cases better.
Seems like a reasonable idea.
I do w
Dear Git users,
It is my pleasure to announce that Git for Windows 2.9.0 is available from:
https://git-for-windows.github.io/
Changes since Git for Windows v2.8.4 (June 7th 2016)
Bug Fixes
??? When running git gc --aggressive or git repack -ald in the presence
of multiple pack f
When we create a signature, it may happen that gpg returns with
"success" but not with an actual detached signature on stdout.
Check for the correct header to catch these cases better.
Signed-off-by: Michael J Gruber
---
This catches at least my echo example.
We could do a full blown gpg signat
On Tue, Jun 14, 2016 at 12:49 AM, Junio C Hamano wrote:
> Christian Couder writes:
>
>> To libify `git apply` functionality we must make 'struct apply_state'
>> usable outside "builtin/apply.c".
>>
>> Let's do that by creating a new "apply.h" and moving
>> 'struct apply_state' there.
>>
>> Signed
On Tue, Jun 14, 2016 at 12:55 AM, Junio C Hamano wrote:
> Christian Couder writes:
>
>> +/*
>> + * Try to apply a patch.
>> + *
>> + * Returns:
>> + * -1 if an error happened
>> + * 0 if the patch applied
>> + * 1 if the patch did not apply
>> + */
>> static int apply_patch(struct apply_sta
Hi,
The attached sample file will cause an out of bounds heap read in the
function gitdiff_verify_name() when passed to git apply.
To reproduce:
* Build git with address sanitizer (-fsanitize=address in cflags)
* git apply --check [path_to_file]
I have pasted the full address sanitizer error tra
Jeff King venit, vidit, dixit 14.06.2016 11:41:
> On Tue, Jun 14, 2016 at 04:39:38PM +0800, ZhenTian wrote:
>
>> I want to set gpg -v to pgp.program, but if I set it, it can't call gpg:
>> ```
>> error: cannot run gpg -v: No such file or directory
>> error: could not run gpg.
>> fatal: failed to w
On Tue, Jun 14, 2016 at 5:22 PM, Jeff King wrote:
> I think the documentation should be updated either way. This is not
> about the ordering in the status table, but rather about the order of
> the real operations. The user may care about that ordering if they want
> to know what races are possibl
On Tue, Jun 14, 2016 at 04:36:59PM +0700, Duy Nguyen wrote:
> On Tue, Jun 14, 2016 at 6:58 AM, Jeff King wrote:
> > This was changed in 10a6cc8 (fetch --prune: Run prune before
> > fetching, 2014-01-02), but it seems that nobody in that
> > discussion realized we were advertising the "after"
> >
Thanks Peff, I have setup to gpg.program, if any progress I will reply.
Over.
Sincerely,
田震
On Tue, Jun 14, 2016 at 5:41 PM, Jeff King wrote:
> On Tue, Jun 14, 2016 at 04:39:38PM +0800, ZhenTian wrote:
>
>> I want to set gpg -v to pgp.program, but if I set it, it can't call gpg:
>> ```
>> error
On Tue, Jun 14, 2016 at 04:39:38PM +0800, ZhenTian wrote:
> I want to set gpg -v to pgp.program, but if I set it, it can't call gpg:
> ```
> error: cannot run gpg -v: No such file or directory
> error: could not run gpg.
> fatal: failed to write commit object
> ```
>
> I have tried set gpg.progra
On Tue, Jun 14, 2016 at 6:58 AM, Jeff King wrote:
> This was changed in 10a6cc8 (fetch --prune: Run prune before
> fetching, 2014-01-02), but it seems that nobody in that
> discussion realized we were advertising the "after"
> explicitly.
Ah... ok. Good to know it's moved up top on purpose becaus
On Tue, Jun 14, 2016 at 12:10 AM, Junio C Hamano wrote:
> Eric Sunshine writes:
>
>> I agree with Junio that moving the sigchain_pop() into the error
>> handling code-path, if possible, would be a nice improvement.
>
> Yeah, "if possible" is really what I was not sure about---is it safe
> to do t
Hi Peff,
I want to set gpg -v to pgp.program, but if I set it, it can't call gpg:
```
error: cannot run gpg -v: No such file or directory
error: could not run gpg.
fatal: failed to write commit object
```
I have tried set gpg.program value to `gpg|/tmp/log`, `/usr/bin/gpg
-v`, `gpg -v`, `"/usr/bi
git 2.9.0 switches the default for diff.renames to true.
Set this to false in config so that the test suite runs unmodified for
old and new git.
Signed-off-by: Michael J Gruber
---
test/tools/libgit.sh | 1 +
1 file changed, 1 insertion(+)
diff --git a/test/tools/libgit.sh b/test/tools/libgit.
On Tue, Jun 14, 2016 at 04:09:52PM +0800, ZhenTian wrote:
> I have tested sign my work in another project, it works fine, I have
> committed five times, all commits are signed.
>
> I can't find encoded signature block in the output of "git cat-file
> commit HEAD", only these:
> ```
> tree 17a572e
Hi Peff,
I commit via this command: gcs -nm "feat: mobile support free freight
hint, closed #1417"
gcs is an alias in zsh, which is: git commit -S
I have tested sign my work in another project, it works fine, I have
committed five times, all commits are signed.
I can't find encoded signature bl
On Tue, Jun 14, 2016 at 03:50:43PM +0800, ZhenTian wrote:
> I commit with -S argument, and I got some output like this:
>
> You need a passphrase to unlock the secret key for
> user: "Tian Zhen "
> 4096-bit RSA key, ID 2EF2AD6E, created 2016-05-21
>
> [master d107770] feat: mobile support free f
On Mon, Jun 13, 2016 at 08:14:43PM -0400, Keith McGuigan wrote:
> Right. The string_list ends up getting (potentially) populated with a
> mix of dup'd and borrowed values. I figured it was safer to leak here
> (especially as we're on the way out anyway), than free memory that
> shouldn't be free
Hi git developers,
I commit with -S argument, and I got some output like this:
You need a passphrase to unlock the secret key for
user: "Tian Zhen "
4096-bit RSA key, ID 2EF2AD6E, created 2016-05-21
[master d107770] feat: mobile support free freight hint, closed #1417
8 files changed, 58 insert
88 matches
Mail list logo
