Re: [RFC] Proposed questions for "Git User's Survey 2016"

On 21 August 2016 at 04:56, Jakub Narębski wrote: > 25. What [channel(s)] do you use to request/get help about Git [(if any)] It may also be useful to ask how people hear news about git, such as when a new release comes out. Not sure if worth a separate question, as there is a

Re: Editing a typo in the message given to "git commit"

Pranit Bauva wrote: > On Sun, Aug 21, 2016 at 8:49 PM, wrote: > > I am learning how to use git. I would like to know: > > > > How can I correct a typo in the message I gave to an old "git commit"? I see > > that the typo occurs in exactly two files in .git:

hello git

good morning git http://s-catalog.online/everywhere.php?bear=1pms6hakx989f bbenta -- 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

Re: Minor bug: git config ignores empty sections

W dniu 16.08.2016 o 14:36, Jeff King pisze: > What I think would be much more sane in general is to parse the whole > thing into a tree (or even a flat list of events), List of events is cheaper on memory (though I don't think there is an issue with size of config file), and can be turned into

Re: [L10N] Kickoff of translation for Git 2.10.0 round 1

2016-08-21 2:38 GMT+08:00 Jean-Noël AVILA : > On samedi 20 août 2016 11:03:00 CEST Junio C Hamano wrote: >> Jean-Noël AVILA writes: >> > 1. In config.c, the changes to the function die_bad_number tried to >> > flatten the translated strings (no message

Re: Editing a typo in the message given to "git commit"

Hey Norman, On Sun, Aug 21, 2016 at 8:49 PM, wrote: > I am learning how to use git. I would like to know: > > How can I correct a typo in the message I gave to an old "git commit"? I see > that the typo occurs in exactly two files in .git: > > .git/logs/refs/heads/master >

Editing a typo in the message given to "git commit"

I am learning how to use git. I would like to know: How can I correct a typo in the message I gave to an old "git commit"? I see that the typo occurs in exactly two files in .git: .git/logs/refs/heads/master .git/logs/HEAD /usr/bin/file says that they are both ASCII English text. So I could

[PATCH 1/3] i18n: fix typos for translation

Signed-off-by: Jean-Noel Avila --- bisect.c| 10 +- sequencer.c | 2 +- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/bisect.c b/bisect.c index 6f512c2..b9a0701 100644 --- a/bisect.c +++ b/bisect.c @@ -760,7 +760,7 @@ static void

[PATCH 2/3] i18n: fix git rebase interactive commit messages

For proper i18n, the logic cannot embed english specific processing. Signed-off-by: Jean-Noel Avila --- git-rebase--interactive.sh | 16 1 file changed, 16 deletions(-) diff --git a/git-rebase--interactive.sh b/git-rebase--interactive.sh index

[PATCH 3/3] i18n: simplify numeric error reporting

Signed-off-by: Jean-Noel Avila --- config.c | 43 +++ 1 file changed, 15 insertions(+), 28 deletions(-) diff --git a/config.c b/config.c index 584cacf..e33c703 100644 --- a/config.c +++ b/config.c @@ -655,43 +655,30 @@ static void

Re: Extending "extended SHA1" syntax to traverse through gitlinks?

On Sun, Aug 21, 2016 at 03:46:36PM +0200, Jakub Narębski wrote: > W dniu 21.08.2016 o 00:50, Josh Triplett pisze: > > Currently, if you have a branch "somebranch" that contains a gitlink > > "somecommit", you can write "somebranch:somecommit" to refer to the > > commit, just like a tree or blob.

Re: Adding more namespace support to git

On Sun, Aug 21, 2016 at 12:30:16PM +0100, Richard wrote: > On 21 August 2016 at 03:05, Josh Triplett wrote: > > Unfortunately, I think at this point, GIT_NAMESPACE has to exclusively > > refer to the namespace for the remote end, to avoid breakage. Which > > means any

Re: Extending "extended SHA1" syntax to traverse through gitlinks?

W dniu 21.08.2016 o 00:50, Josh Triplett pisze: > Currently, if you have a branch "somebranch" that contains a gitlink > "somecommit", you can write "somebranch:somecommit" to refer to the > commit, just like a tree or blob. ("man git-rev-parse" defines this > syntax in the "SPECIFYING

Re: Adding more namespace support to git

On 21 August 2016 at 03:05, Josh Triplett wrote: > On Sat, Aug 20, 2016 at 08:07:00PM +0100, Richard wrote: >> Since when upload-pack and receive-pack run hooks they leave GIT_NAMESPACE >> set >> there are hook scripts that expect that the current namespace is ignored, >>

Re: [PATCH v13 04/13] bisect--helper: `bisect_clean_state` shell function in C

Hey, On Sat, Aug 20, 2016 at 2:02 AM, Pranit Bauva wrote: > Reimplement `bisect_clean_state` shell function in C and add a > `bisect-clean-state` subcommand to `git bisect--helper` to call it from > git-bisect.sh . > > Using `--bisect-clean-state` subcommand is a measure

Re: [PATCH v13 01/13] bisect--helper: use OPT_CMDMODE instead of OPT_BOOL

Hey everyone, On Sat, Aug 20, 2016 at 2:02 AM, Pranit Bauva wrote: > `--next-all` is meant to be used as a subcommand to support multiple > "operation mode" though the current implementation does not contain any > other subcommand along side with `--next-all` but further

Re: Most recent revision that contains a string

On Sun, Aug 21, 2016 at 10:13:33AM +0200, Andreas Schwab wrote: > On Aug 20 2016, Josh Triplett wrote: > > If you want to find a change that introduces or removes a particular > > string, you could use "git log -S". That doesn't allow regexes, > > It does, actually, see

Re: Most recent revision that contains a string

On Aug 20 2016, Josh Triplett wrote: > If you want to find a change that introduces or removes a particular > string, you could use "git log -S". That doesn't allow regexes, It does, actually, see --pickaxe-regex. Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG