Re: Looking for help to understand external filter driver code

On Tue, Jul 19, 2016 at 02:33:09PM -0700, Junio C Hamano wrote: > > Git writes --> 4 byte content length > > Git writes --> content string > > Git reads <-- 4 byte filtered content length > > Git reads <-- filtered content > > Do you really need to force the sender to know the length in >

Re: Looking for help to understand external filter driver code

> On 20 Jul 2016, at 10:59, Jakub Narębski wrote: > > W dniu 2016-07-19 o 23:33, Junio C Hamano pisze: >> Lars Schneider writes: >> Git writes --> 4 byte filename length Git writes --> filename string >> >> Why limit to 32GB? Perhaps NUL

Re: Looking for help to understand external filter driver code

W dniu 2016-07-19 o 23:33, Junio C Hamano pisze: > Lars Schneider writes: > >> > Git writes --> 4 byte filename length >> > Git writes --> filename string > > Why limit to 32GB? Perhaps NUL termination is more appropriate > here? Errr, I think limiting _filename_ to

Re: Looking for help to understand external filter driver code

On 07/20/2016 12:01 AM, Lars Schneider wrote: On 19 Jul 2016, at 23:33, Junio C Hamano wrote: Lars Schneider writes: Git writes --> 4 byte filename length Git writes --> filename string Why limit to 32GB? Perhaps NUL termination is more

Re: Looking for help to understand external filter driver code

On 19 Jul 2016, at 23:33, Junio C Hamano wrote: > Lars Schneider writes: > >> Git writes --> 4 byte filename length >> Git writes --> filename string > > Why limit to 32GB? Perhaps NUL termination is more appropriate > here? OK, I will use NUL

Re: Looking for help to understand external filter driver code

Lars Schneider writes: > Git writes --> 4 byte filename length > Git writes --> filename string Why limit to 32GB? Perhaps NUL termination is more appropriate here? > Git writes --> 4 byte content length > Git writes --> content string > Git reads <-- 4 byte filtered

Re: Looking for help to understand external filter driver code

On 19 Jul 2016, at 20:53, Junio C Hamano wrote: > Junio C Hamano writes: > >> The key benefit of this arrangement is the above can be done without >> having to do poll() to flip between reading and writing that is >> needed to avoid deadlocking, which

Re: Looking for help to understand external filter driver code

Junio C Hamano writes: > The key benefit of this arrangement is the above can be done without > having to do poll() to flip between reading and writing that is > needed to avoid deadlocking, which kept the code simpler. A later > conversion of the write side into async does

Re: Looking for help to understand external filter driver code

an obvious answer... but can anyone > help me to understand the code and explain why we fork twice? In "git show aa4ed4" you find this picture: /* * Create a pipeline to have the command filter the buffer's * contents. * * (child --> cm

Looking for help to understand external filter driver code

Hi, a long time ago in aa4ed4 Junio introduced the external filter driver definition. Since that time we fork the Git process and then we fork again to run the external filter. This is probably a super stupid question with an obvious answer... but can anyone help me to understand the code

[PATCH v5 29/38] i18n: merge: change command option help to lowercase

Change command option description to lowercase, matching pull counterpart option. Translators would have to translate such message only once. Signed-off-by: Vasco Almeida --- builtin/merge.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

Re: `git help svn` missing description of `propset`

with a patch. thank you, -Alfred On 6/7/16 1:08 PM, Eric Wong wrote: +Cc Alfred, David Joseph Pecoraro <pecor...@apple.com> wrote: `git help svn` does not mention `propset` but it does mention `proplist` and `propget`. This seems like an oversight. $ git he

Re: `git help svn` missing description of `propset`

+Cc Alfred, David Joseph Pecoraro <pecor...@apple.com> wrote: > `git help svn` does not mention `propset` but it does mention `proplist` and > `propget`. This seems like an oversight. > > > $ git help svn > ... > proplist >

[PATCH v4 29/38] i18n: merge: change command option help to lowercase

Change command option description to lowercase, matching pull counterpart option. Translators would have to translate such message only once. Signed-off-by: Vasco Almeida --- builtin/merge.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

`git help svn` missing description of `propset`

`git help svn` does not mention `propset` but it does mention `proplist` and `propget`. This seems like an oversight. $ git help svn ... proplist Lists the properties stored in the Subversion repository about a given file or directory. Use -r/--revision

[PATCH v3 30/39] i18n: merge: change command option help to lowercase

Change command option description to lowercase, matching pull counterpart option. Translators would have to translate such message only once. Signed-off-by: Vasco Almeida --- builtin/merge.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

Re: [PATCH] Documentation: add instructions to help setup gmail 2FA

On Fri, May 27, 2016 at 5:06 PM, Junio C Hamano wrote: > Michael Rappazzo writes: > >> For those who use two-factor authentication with gmail, git-send-email >> will not work unless it is setup with an app-specific password. The >> example for setting up

Re: [PATCH] Documentation: add instructions to help setup gmail 2FA

Michael Rappazzo writes: > For those who use two-factor authentication with gmail, git-send-email > will not work unless it is setup with an app-specific password. The > example for setting up git-send-email for use with gmail will now > include information on generating and

[PATCH] Documentation: add instructions to help setup gmail 2FA

For those who use two-factor authentication with gmail, git-send-email will not work unless it is setup with an app-specific password. The example for setting up git-send-email for use with gmail will now include information on generating and storing the app-specific password. ---

Re: [PATCH 04/10] shell helpers usage: always send help to stderr

ste in designing these things... On Mon, May 2, 2016 at 5:45 PM, Junio C Hamano <gits...@pobox.com> wrote: > Stefan Beller <sbel...@google.com> writes: > >> git --help |grep pull >> >> instead of >> >> git --help 2>&1 |grep pull > > Not jus

Re: [PATCH 04/10] shell helpers usage: always send help to stderr

Stefan Beller <sbel...@google.com> writes: > git --help |grep pull > > instead of > > git --help 2>&1 |grep pull Not just that. It makes me sad that it is unpredictable which stream a project happens to have chosen to send its help text and I end up alm

Re: [PATCH 04/10] shell helpers usage: always send help to stderr

the usage on >> stdout. Unify displaying help for shell commands on stderr. > > The primary output from "git cmd --help" is the usage message. It > is debatable why it should go to the standard error output when it > is the primary thing the user asked for. I had written some

Re: [PATCH 04/10] shell helpers usage: always send help to stderr

Stefan Beller <sbel...@google.com> writes: > `git submodule asdf` would trigger displaying the usage of the submodule > command on stderr, however `git submodule -h` would display the usage on > stdout. Unify displaying help for shell commands on stderr. The primary output from

[PATCH 04/10] shell helpers usage: always send help to stderr

`git submodule asdf` would trigger displaying the usage of the submodule command on stderr, however `git submodule -h` would display the usage on stdout. Unify displaying help for shell commands on stderr. Signed-off-by: Stefan Beller <sbel...@google.com> --- git-sh-setup.sh | 2 +-

Re: [ANNOUNCE] Git v2.8.1 (and call-for-help to "make rpmbuild" users)

target, before I make an announcement, here is a call-for-help to > you. > > Git v2.8 removed README file and added a corresponding README.md > file. The change however did not adjust git.spec.in that still > referred to README, causing "make rpmbuild" to fail. The breakage

Re: [ANNOUNCE] Git v2.8.1 (and call-for-help to "make rpmbuild" users)

, before I make an announcement, here is a call-for-help to > you. > > Git v2.8 removed README file and added a corresponding README.md > file. The change however did not adjust git.spec.in that still > referred to README, causing "make rpmbuild" to fail. The breakage > was n

[ANNOUNCE] Git v2.8.1 (and call-for-help to "make rpmbuild" users)

If you do not build RPM binary packages from our pristine source, you can safely ignore this release and stop reading this message. Now that the audience of this message has been limited to a narrow target, before I make an announcement, here is a call-for-help to you. Git v2.8 removed README

Re: git alias quoting help

On Fri, Apr 1, 2016 at 7:05 AM, Christian Couder wrote: > On Wed, Mar 30, 2016 at 6:13 AM, shawn wilson wrote: >> I've also tried to make this a plain bash script (w/o the function or >> if statements and am failing at the same place). The issue

Re: git alias quoting help

On Wed, Mar 30, 2016 at 6:13 AM, shawn wilson wrote: > I've also tried to make this a plain bash script (w/o the function or > if statements and am failing at the same place). The issue seems to be > with the quoting in the filter-branch | ls-files bit. Also, the end > goal

Re: git alias quoting help

I think I finally figured out how I want to do this: git remote add temp ..// git fetch temp git merge -s ours --no-commit temp/master git read-tree --prefix= -u temp/master: git commit -m "foo" However, when I do this, I've got all of the commits from the original (temp) repo. How do I prune

Re: git alias quoting help

FWIW, I (finally) found two projects that like they'll do what I want: git-splits and git_filter The later was lacking in documentation and after the build I couldn't figure it out at a glance and I think git-splits will DWIW. On Thu, Mar 31, 2016 at 10:27 AM, shawn wilson

Re: git alias quoting help

BTW, just trying to get filter-branch to interpret the bash script string correctly now and it still isn't working: git filter-branch -f --prune-empty --index-filter "\ git ls-files -s | \ sed \"s-\\t\\\"*-&${1}-\" | \ GIT_INDEX_FILE=\$GIT_INDEX_FILE.new \ git update-index --index-info &&

git alias quoting help

I've also tried to make this a plain bash script (w/o the function or if statements and am failing at the same place). The issue seems to be with the quoting in the filter-branch | ls-files bit. Also, the end goal here is to be able to move a directory from one repo and keep the history. While

Re: git difftool help

On Tue, Mar 29, 2016 at 3:07 AM, ratheesh kannoth <ratheesh@gmail.com> wrote: > 'git diff 'is opening in meld. I could not create a patch using - git > diff > ./patch-01 > i did not make any change to pick meld, by default it is picking meld. > > > Which "g

Best regards! Dear Sir or Madam! - please help our site - пожалуйста, помогите нашему сайту - будь ласка, допоможіть нашому сайту http://edu-community.pp.ua/

Best regards! 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...@edu-community.pp.ua http://edu-community.pp.ua/ добрий день, просимо на будь-якій сторінці вгорі один раз натиснути на

git difftool help

'git diff 'is opening in meld. I could not create a patch using - git diff > ./patch-01 i did not make any change to pick meld, by default it is picking meld. Which "git difftool" will help to create patch ? i do want to use format patch as changes are not yet committed

Re: [PATCH 2/2] completion: add 'revisions' and 'everyday' to 'git help'

"Philip Oakley" <philipoak...@iee.org> writes: >> The first step may be to teach a new subcommand to "git help" >> to show a list of these words, and then _git_help can use it to >> lazily compute the list just like __git_commands does. > > 'g

Re: [PATCH 2/2] completion: add 'revisions' and 'everyday' to 'git help'

lly that we have to maintain this list to be in sync with the set of documents we offer. Wouldn't it make more sense to go in the direction of _removing_ this list of hardcoded words here? The first step may be to teach a new subcommand to "git help" to show a list of these words, and then

Re: [PATCH 2/2] completion: add 'revisions' and 'everyday' to 'git help'

be in sync with the set of documents we offer. Wouldn't it make more sense to go in the direction of _removing_ this list of hardcoded words here? The first step may be to teach a new subcommand to "git help" to show a list of these words, and then _git_help can use it to lazily compute the

Re: [PATCH 1/2] completion: add option '--guides' to 'git help'

Ralf Thielow writes: > Signed-off-by: Ralf Thielow > --- > contrib/completion/git-completion.bash | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) Sounds sensible. Thanks. > > diff --git a/contrib/completion/git-completion.bash >

[PATCH 2/2] completion: add 'revisions' and 'everyday' to 'git help'

Signed-off-by: Ralf Thielow --- contrib/completion/git-completion.bash | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/contrib/completion/git-completion.bash b/contrib/completion/git-completion.bash index 70f4171..ffe6004 100644 ---

[PATCH 0/2] completion: git-help: add missing option and params

The bash completion is missing the option '--guides' for 'git-help' and some params you see there. Add them both. Ralf Thielow (2): completion: add option '--guides' to 'git help' completion: add 'revisions' and 'everyday' to 'git help' contrib/completion/git-completion.bash | 6 +++--- 1

[PATCH 1/2] completion: add option '--guides' to 'git help'

Signed-off-by: Ralf Thielow --- contrib/completion/git-completion.bash | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/contrib/completion/git-completion.bash b/contrib/completion/git-completion.bash index e3918c8..70f4171 100644 ---

With best regards! Dear Sir or Madam! - please help our school site - пожалуйста, помогите нашему сайту - будь ласка, допоможіть нашому сайту http://school-site.kiev.ua/

With best regards! 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 school site, Thank you ad...@school-site.kiev.ua http://school-site.kiev.ua/ добрий день, просимо на будь-якій сторінці вгорі один раз натиснути

Re: [PATCH] gitk: Follow themed bgcolor in help dialogs

On Thu, Feb 04, 2016 at 03:32:19AM +0100, Guillermo S. Romero wrote: > Make Help > About & Key bindings dialogs readable if theme > has changed font color to something incompatible with white. > > Signed-off-by: Guillermo S. Romero <gsrom...@infernal-iceberg.com&g

Re: Bug#813084: Background git gc fails, telling me to run git prune, which doesn't help

Control: forwarded -1 git@vger.kernel.org On Fri, 2016-01-29 at 21:05 +0700, Duy Nguyen wrote: > On Fri, Jan 29, 2016 at 8:35 PM, Ben Hutchings wrote: > > git keeps trying to do a background gc on my linux repository, but > > fails, reporting this in .git/gc.log: > > > >

Kind regards! Dear Sir or Madam! - please help our school site - пожалуйста, помогите нашему школьному сайту - будь ласка, допоможіть нашому шкільному сайту http://40030ssch2.pp.ua/

Kind regards! 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 school site, Thank you ad...@40030ssch2.pp.ua http://40030ssch2.pp.ua/ добрий день, просимо на будь-якій сторінці вгорі один раз натиснути на

Good day! Dear Sir or Madam! - please help our school site - пожалуйста, помогите нашему школьному сайту - будь ласка, допоможіть нашому шкільному сайту http://bilokaminsky-nvk.pp.ua/

Good day! 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 school site, Thank you ad...@bilokaminsky-nvk.pp.ua http://bilokaminsky-nvk.pp.ua/ добрий день, просимо на будь-якій сторінці вгорі один раз натиснути на

Best regards! Dear Sir or Madam! - please help our school site - пожалуйста, помогите нашему школьному сайту - будь ласка, допоможіть нашому шкільному сайту http://bilokaminsky-nvk.pp.ua/

Best regards! 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 school site, Thank you ad...@bilokaminsky-nvk.pp.ua http://bilokaminsky-nvk.pp.ua/ добрий день, просимо на будь-якій сторінці вгорі один раз

[PATCH] gitk: Follow themed bgcolor in help dialogs

Make Help > About & Key bindings dialogs readable if theme has changed font color to something incompatible with white. Signed-off-by: Guillermo S. Romero <gsrom...@infernal-iceberg.com> --- Hi: Found more places where themable colors makes things unreadable because not every

Dear Sir or Madam! - please help our site - пожалуйста, помогите нашему сайту - будь ласка, допоможіть нашому сайту http://petition.kiev.ua/

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/ добрий день, просимо на будь-якій сторінці вгорі один раз натиснути на рекламний банер, щоб ми

[PATCH] Consistent usage of working tree in the git-add help

The usage of working directory is inconsistent in the git add help. Also http://git-scm.com/docs/git-clone speaks only about working tree. Remaining entry found by "git grep -B1 '^directory' git-add.txt" really relates to a directory. Signed-off-by: Lars Vogel <lars.vo..

Re: [PATCH] Consistent usage of working tree in the git-add help

Thanks Junio for the feedback. I send a new patch with only the first change. On Thu, Jan 21, 2016 at 1:24 AM, Junio C Hamano <gits...@pobox.com> wrote: > Lars Vogel <lars.vo...@gmail.com> writes: > >> The usage of working directory is inconsistent in the git add help. &g

Re: [PATCH] Consistent usage of working tree in the git-add help

Lars Vogel <lars.vo...@gmail.com> writes: > The usage of working directory is inconsistent in the git add help. > Also http://git-scm.com/docs/giit-clone speaks only about working tree. > Remaining entry found by "git grep -B1 '^directory' git-add.txt" really > relate

Dear Sir or Madam, let the New Year be more successful for you! - please help our site - пожалуйста, помогите нашему сайту - будь ласка, допоможіть нашому сайту http://kyiv230school.pp.ua/

Dear Sir or Madam, let the New Year be more successful for you! good day, ask at the top of any page click once on the banner, so that we could pay for hosting our site, Thank you ad...@kyiv230school.pp.ua http://kyiv230school.pp.ua/ добрий день, просимо на будь-якій сторінці вгорі один раз

[PATCH/RFC 1/2] describe: mention glob in the --matches help text

This saves the user from needing to consult to manpage to learn the format of the --matches argument. Signed-off-by: Mostyn Bramley-Moore --- builtin/describe.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/builtin/describe.c b/builtin/describe.c

Re: Help debugging git-svn

Ok I came up with another idea to avoid having to deal with the old svn history (I'm having no problems fetching/dcommitting with my current repo). I already have the branches I work with, the thing is that the revisions I fetched before I started using the svn authors file have nasty IDs

Re: Help debugging git-svn

On Fri, Dec 18, 2015 at 11:28 AM, Edmundo Carmona Antoranz wrote: > Ok I came up with another idea to avoid having to deal with the > old svn history (I'm having no problems fetching/dcommitting with my > current repo). I already have the branches I work with, the thing

Re: Help debugging git-svn

On Wed, Dec 16, 2015 at 1:41 AM, Eric Wong wrote: > > Any chance you can reproduce this on a Linux system? > I do not use non-Free systems and have no debugging experience > there at all. > My wish But it's a big resounding "no". >> With my very flawed knowledge of

Help debugging git-svn

Hello, Eric, Everybody! I need your help getting git-svn to clone a repository. I had already cloned it once but then a few months ago I discovered the authors map file and it's like the first time I did a checkout using git well, perhaps not that much, but close. Seeing the real names

Re: Help debugging git-svn

Edmundo Carmona Antoranz wrote: > 1 [main] perl 5652 cygwin_exception::open_stackdumpfile: Dumping stack > trace to perl.exe.stackdump > > And then, in the file: > > Exception: STATUS_ACCESS_VIOLATION at rip=0048360C10C > rax=000601E4BFF8 rbx=5219E248

Success in your activities - please help our site - пожалуйста, помогите нашему сайту - будь ласка, допоможіть нашому сайту http://wellness-hotels.pp.ua/

Success in your activities good day, ask at the top of any page click once on the banner, so that we could pay for hosting our site, Thank you wellnesshotels...@gmail.com http://wellness-hotels.pp.ua/ добрий день, просимо на будь-якій сторінці вгорі один раз натиснути на рекламний банер, щоб ми

Re: [PATCH 2/1] stash: recognize "--help" for subcommands

On Wed, May 20, 2015 at 8:17 PM, Jeff King <p...@peff.net> wrote: > On Wed, May 20, 2015 at 02:01:32PM -0400, Jeff King wrote: > >> This takes away the immediate pain. We may also want to >> teach "--help" to the option. I guess we cannot do better >>

git worktree help inconsistent

Using git 2.6.1 In git command line usage, Please mark optional, the man page is correct. $ git worktree add usage: git worktree add [] or: git worktree prune [] -f, --force checkout even if already checked out in other worktree -bcreate a new branch -B

[PATCH 31/68] help: drop prepend function in favor of xstrfmt

This function predates xstrfmt, and its functionality is a subset. Let's just use xstrfmt. Signed-off-by: Jeff King --- builtin/help.c | 14 ++ 1 file changed, 2 insertions(+), 12 deletions(-) diff --git a/builtin/help.c b/builtin/help.c index 3422e73..fba8c01 100644

[PATCH 59/68] help: clean up kfmclient munging

When we are going to launch "/path/to/konqueror", we instead rewrite this into "/path/to/kfmclient" by duplicating the original string and writing over the ending bits. This can be done more obviously with strip_suffix and xstrfmt. Note that we also fix a subtle bug with the "filename" parameter,

[PATCH 58/67] help: clean up kfmclient munging

When we are going to launch "/path/to/konqueror", we instead rewrite this into "/path/to/kfmclient" by duplicating the original string and writing over the ending bits. This can be done more obviously with strip_suffix and xstrfmt. Note that we also fix a subtle bug with the "filename" parameter,

[PATCH 31/67] help: drop prepend function in favor of xstrfmt

This function predates xstrfmt, and its functionality is a subset. Let's just use xstrfmt. Signed-off-by: Jeff King --- builtin/help.c | 14 ++ 1 file changed, 2 insertions(+), 12 deletions(-) diff --git a/builtin/help.c b/builtin/help.c index 3422e73..fba8c01 100644

[PATCHv3 0/2] 'git config --names-only' to help the completion script

This is a reroll of 'sg/config-name-only'. * Instead of the two new listing options of the previous round add one new option '--names-only' to modify the output of '--list' and '--get-regexp' options, as suggested in previous discussions. * Reorganized the commit messages: don't go

[PATCH v11 02/10] Documentation/bisect: move getting help section to the end

/Documentation/git-bisect.txt @@ -31,12 +31,6 @@ This command uses 'git rev-list --bisect' to help drive the binary search process to find which change introduced a bug, given an old good commit object name and a later bad commit object name. -Getting help - - -Use git bisect to get

[PATCH v10 2/7] Documentation/bisect: move getting help section to the end

/Documentation/git-bisect.txt @@ -31,12 +31,6 @@ This command uses 'git rev-list --bisect' to help drive the binary search process to find which change introduced a bug, given an old good commit object name and a later bad commit object name. -Getting help - - -Use git bisect to get

Re: Need some help on patching buildin-files // was: Looking for feedback and help with a git-mirror for local usage

On Fri, Jun 12, 2015 at 12:52:44PM +0200, Bernd Naumann wrote: Hello again, After digging the code I may have got a clue where to start but I would still appreciate some help from a developer, cause I have never learned to write C. (Some basics at school which happened over a decade ago

Re: Need some help on patching buildin-files // was: Looking for feedback and help with a git-mirror for local usage

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello again, After digging the code I may have got a clue where to start but I would still appreciate some help from a developer, cause I have never learned to write C. (Some basics at school which happened over a decade ago.) Currently I have

Looking for feedback and help with a git-mirror for local usage

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, I have came up with an idea # Yep I know, exactly that kind of e-mail everyone wants to read ;) and I'm working currently on a shell-prototype to face the following situation and problem and need some feedback/advise: I often build in

Re: [PATCH v11 5/5] help: respect new common command grouping

On 05/21/2015 08:04 PM, Eric Sunshine wrote: On Thu, May 21, 2015 at 1:39 PM, Sébastien Guimmara sebastien.guimm...@gmail.com wrote: 'git help' shows common commands in alphabetical order: The most commonly used git commands are: addAdd file contents to the index bisect

Re: [PATCH v11 5/5] help: respect new common command grouping

On Thu, May 21, 2015 at 1:39 PM, Sébastien Guimmara sebastien.guimm...@gmail.com wrote: 'git help' shows common commands in alphabetical order: The most commonly used git commands are: addAdd file contents to the index bisect Find by binary search the change that introduced

[PATCH v10 5/5] help: respect new common command grouping

'git help' shows common commands in alphabetical order: The most commonly used git commands are: addAdd file contents to the index bisect Find by binary search the change that introduced a bug branch List, create, or delete branches checkout Checkout a branch

Re: [PATCH v10 5/5] help: respect new common command grouping

On Thu, May 21, 2015 at 9:13 AM, Sébastien Guimmara sebastien.guimm...@gmail.com wrote: 'git help' shows common commands in alphabetical order: [...] without any indication of how commands relate to high-level concepts or each other. Revise the output to explain their relationship

[PATCH v11 5/5] help: respect new common command grouping

'git help' shows common commands in alphabetical order: The most commonly used git commands are: addAdd file contents to the index bisect Find by binary search the change that introduced a bug branch List, create, or delete branches checkout Checkout a branch

Re: [PATCH v10 5/5] help: respect new common command grouping

the latter half of that sentence as explaining the group labels which we did not have (so we did not have to mention in the original). Hmm, but is it necessary to explain the group labels in the first place? The help output (group labels and all) seems self-explanatory already, and one would expect

Re: [PATCH v10 5/5] help: respect new common command grouping

Eric Sunshine sunsh...@sunshineco.com writes: + + puts(_(These are common Git commands used in various situations:)); The clause in various situations is quite nebulous and thus adds no substance. FWIW I view the latter half of that sentence as explaining the group labels which we did

Re: [PATCH v10 5/5] help: respect new common command grouping

Eric Sunshine sunsh...@sunshineco.com writes: Hmm, but is it necessary to explain the group labels in the first place? The help output (group labels and all) seems self-explanatory already, and one would expect (hope) that readers are intelligent enough to understand implicitly that the group

[BUG, RFC] git stash drop --help

Hello, I stumbled upon something that annoyed me a bit, as I was working with git stash to commit some big pile of modifications in small commits... I wanted to get help wrt git stash drop and did it the following way : [steps to reproduce] mkdir tmp cd tmp git init touch test.txt git add

Re: [PATCH v9 5/5] help: respect new common command grouping

On 20/05/15 20:23, Sébastien Guimmara wrote: 'git help' shows common commands in alphabetical order: The most commonly used git commands are: addAdd file contents to the index bisect Find by binary search the change that introduced a bug branch List, create

Re: [PATCH v9 5/5] help: respect new common command grouping

On 05/20/2015 11:39 PM, Ramsay Jones wrote: On 20/05/15 20:23, Sébastien Guimmara wrote: Helped-by: Eric Sunshine sunsh...@sunshineco.com Signed-off-by: Ramsay Jones ram...@ramsay1.demon.co.uk This should be (at most) 'Helped-by:' - my 'contribution' was so minor that even a 'Helped-by:' is

[PATCH 2/1] stash: recognize --help for subcommands

On Wed, May 20, 2015 at 02:01:32PM -0400, Jeff King wrote: This takes away the immediate pain. We may also want to teach --help to the option. I guess we cannot do better than just having it run git help stash in all cases (i.e., we have no way to get the help for a specific subcommand

[PATCH v9 5/5] help: respect new common command grouping

'git help' shows common commands in alphabetical order: The most commonly used git commands are: addAdd file contents to the index bisect Find by binary search the change that introduced a bug branch List, create, or delete branches checkout Checkout a branch

Re: [PATCH v8 5/5] help: respect new common command grouping

Sébastien Guimmara sebastien.guimm...@gmail.com writes: 'git help' shows common commands in alphabetical order: The most commonly used git commands are: addAdd file contents to the index bisect Find by binary search the change that introduced a bug branch List

Re: [PATCH v7 0/5] git help: group common commands by theme

Eric Sunshine sunsh...@sunshineco.com writes: rebased on 'next' (a2776d4) Something to keep in mind for the future: It's usually easier to manage preparatory cleanup patches by incorporating them into the series which needs/wants them rather than posting them as separate topics. That way,

Re: Help with Getting started to Contribute

karthik nayak karthik@gmail.com writes: There is also Junio's Blog where he keeps a list of things to be done http://git-blame.blogspot.de/p/leftover-bits.html I'd add this: https://git.wiki.kernel.org/index.php/SmallProjectsIdeas -- Matthieu Moy http://www-verimag.imag.fr/~moy/ -- To

Help with Getting started to Contribute

Hi , I would like to contribute to git. Can you guys point me to some useful resources to get me started to contribute to git. Also does git have something like junior jobs so that It can be done by new to contribution. Also searching about the git in google points to some other organisation

Re: Help with Getting started to Contribute

Hello Tummala, On 04/28/2015 07:15 PM, Tummala Dhanvi wrote: Hi , I would like to contribute to git. Can you guys point me to some useful resources to get me started to contribute to git. I suggest you go through the Documentation, especially Documentation/CodingGuidelines and

Re: [PATCH] grep: correctly initialize help-all option

)default_pager }, OPT_BOOL(0, ext-grep, external_grep_allowed__ignored, N_(allow calling of grep(1) (ignored by this build))), - { OPTION_CALLBACK, 0, help-all, options, NULL, N_(show usage), + { OPTION_CALLBACK, 0, help-all, opt

[PATCH] grep: correctly initialize help-all option

The help-all option is being initialized with a wrong value. While being semantically wrong this can also cause a gcc segmentation fault on ARMv7 hardfloat platforms with a hardened toolchain. Fix this by initializing with the correct value. --- builtin/grep.c | 2 +- 1 file changed, 1 insertion

[PATCH v2] grep: correctly initialize help-all option

The help-all option is being initialized with a wrong value. While being semantically wrong this can also cause a segmentation fault in gcc on ARMv7 hardfloat platforms with a hardened toolchain. Fix this by initializing with a NULL value. Signed-off-by: Patrick Steinhardt p...@pks.im --- Added

Re: [PATCH] grep: correctly initialize help-all option

On Thu, Apr 9, 2015 at 9:41 AM, Patrick Steinhardt p...@pks.im wrote: The help-all option is being initialized with a wrong value. While being semantically wrong this can also cause a gcc segmentation fault on ARMv7 hardfloat platforms with a hardened toolchain. Fix this by initializing

Re: Git ignore help

On Tue, Mar 24, 2015 at 7:46 PM, mdc...@seznam.cz wrote: Duy, you wrote: This is true. To elaborate, if we have to recurse in excluded directories so that we can include some back, then the reason for excluding is already defeated as we may need to traverse the entire directory structure.

Re: Git ignore help

-- Od: Duy Nguyen Komu: Eric Sunshine Datum: 24. 3. 2015 10:40:33 Předmět: Re: Git ignore help On Tue, Mar 24, 2015 at 8:55 AM, Eric Sunshine wrote: e.g. db, reports or scripts, we could keep going for a while. I think I attempted to do this in the past and failed (don't remember

Re: Git ignore help

On Tue, Mar 24, 2015 at 8:55 AM, Eric Sunshine sunsh...@sunshineco.com wrote: e.g. db, reports or scripts, we could keep going for a while. I think I attempted to do this in the past and failed (don't remember exactly why). Maybe I'll try again some time in future. I also was pretty sure that

Re: Git ignore help

of the performance implications, I guess it would be ok. So it's back in my back log. How much does a config variable actually help? In a sense, one could argue that this is already an opt-in feature since it requires crafting gitignore in a particular fashion. Existing projects which have (properly

<    1   2   3   4   5   6   7   8   9   10   >