If option --help is passed to a Git command, we try to open
the man page of that command. However, we do it even for commands
we don't know. Make sure the command is known to Git before try
to open the man page. If we don't know the command, give the
usual advice.
Signed-off-by: Ra
On Fri, Aug 12, 2016 at 9:25 AM, Junio C Hamano wrote:
> On Fri, Aug 12, 2016 at 9:15 AM, Joseph Musser wrote:
>> Oh, I'm embarrassed. The typo was mine, I must have typed `git stack
>> --help`. I would have expected a syntax error message or "did you
>> mean&quo
On Fri, Aug 12, 2016 at 9:15 AM, Joseph Musser wrote:
> Oh, I'm embarrassed. The typo was mine, I must have typed `git stack
> --help`. I would have expected a syntax error message or "did you
> mean" suggestions; it didn't even enter my mind that it would look up
>
Oh, I'm embarrassed. The typo was mine, I must have typed `git stack
--help`. I would have expected a syntax error message or "did you
mean" suggestions; it didn't even enter my mind that it would look up
whatever I typed before --help and assume it existed on disk.
I'
> On 12 Aug 2016, at 17:48, Junio C Hamano wrote:
>
> Joseph Musser writes:
>
>> Looks like a simple typo.
>
> Unfortunately this does not reproduce to me (built from source on
> Ubuntu Linux).
I tried it with the latest released version on Windows and OSX (2.9.2)
and was not able to reprodu
Joseph Musser writes:
> Looks like a simple typo.
Unfortunately this does not reproduce to me (built from source on
Ubuntu Linux).
--
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.or
Looks like a simple typo.
Joseph Musser
--
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
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
> advance
> 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 termination is more appropriate
>> here?
>
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 32GB is a reasonable
assumpt
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 appropriate
here?
OK, I will use NUL terminatio
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 termination for the filename.
You're also right
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 content length
> Git reads
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 kept the code simpler. A later
>> convers
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 not fundamentally
> c
Lars Schneider writes:
> 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 anyo
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 and
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 a/builtin/merge.c b/builtin/merge.c
ind
in a week hopefully with a patch.
thank you,
-Alfred
On 6/7/16 1:08 PM, Eric Wong wrote:
+Cc Alfred, David
Joseph Pecoraro wrote:
`git help svn` does not mention `propset` but it does mention `proplist` and
`propget`. This seems like an oversight.
$ git help svn
.
+Cc Alfred, David
Joseph Pecoraro wrote:
> `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 Sub
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 a/builtin/merge.c b/builtin/merge.c
ind
`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
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 a/builtin/merge.c b/builtin/merge.c
ind
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 git-send-email for use with gmail will now
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 storing the app-speci
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.
---
Documentation/gi
in designing these things...
On Mon, May 2, 2016 at 5:45 PM, Junio C Hamano wrote:
> Stefan Beller writes:
>
>> git --help |grep pull
>>
>> instead of
>>
>> git --help 2>&1 |grep pull
>
> Not just that. It makes me sad that it is unpredictable whi
Stefan Beller 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 almost always doing
rand
On Mon, May 2, 2016 at 4:28 PM, Junio C Hamano wrote:
> Stefan Beller 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
Stefan Beller 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 "git cmd --help" i
`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
---
git-sh-setup.sh | 2 +-
1 file changed, 1 insertion
ouncement, 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 not noticed by anyb
efore 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 not n
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
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 seems to be
>> with the quoting in the filter-branc
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 here is to be able to m
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 the
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 wrote:
> BTW, just tryi
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 &&
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 this
On Tue, Mar 29, 2016 at 3:07 AM, ratheesh kannoth
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 "git difftool" will
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 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 commit
"Philip Oakley" 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.
>
> 'git help -a' (or --al
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 list just like __git_commands does.
t 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 list just like __git_commands does.
But this change
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
> b/contrib/completion/git-completion.bash
> index e3918
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
--- a/contrib/completion/git-completion.bas
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 '
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
--- a/contrib/completion/git-completion.bash
++
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/
добрий день,
просимо на будь-якій сторінці вгорі один раз натиснути
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
Thanks, applied.
Paul.
--
To unsubscribe f
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:
> >
> > warning: There are too m
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 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 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/
добрий день,
просимо на будь-якій сторінці вгорі один раз натиснути
Make Help > About & Key bindings dialogs readable if theme
has changed font color to something incompatible with white.
Signed-off-by: Guillermo S. Romero
---
Hi:
Found more places where themable colors makes things unreadable
because not everything adapted to the changed style.
GSR
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/
добрий день,
просимо на будь-якій сторінці вгорі один раз натиснути на рекламний банер,
щоб ми змогл
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
---
Documenta
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 wrote:
> Lars Vogel writes:
>
>> The usage of working directory is inconsistent in the git add help.
>> Also http://git-scm.com/docs/giit-clone speaks
Lars Vogel 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
> relates to a director
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/
добрий день,
просимо на будь-якій сторінці вгорі один раз нати
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
index 8a25abe..2386c64
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 is
> that the revisions
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 inste
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 perl I have seen that the
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 rcx=00060003A590
> rdx=0
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
nam
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/
добрий день,
просимо на будь-якій сторінці вгорі один раз натиснути на рекламний банер,
щоб ми
On Wed, May 20, 2015 at 8:17 PM, Jeff King 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
>> than just having it run
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
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
--- a/builtin/h
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,
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,
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
--- a/builtin/h
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 int
-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 &qu
-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 &qu
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
-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
-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 example
On 05/21/2015 08:04 PM, Eric Sunshine wrote:
On Thu, May 21, 2015 at 1:39 PM, 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
On Thu, May 21, 2015 at 1:39 PM, 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 int
'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
Eric Sunshine 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
>> substance.
>
> FWIW I view 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 an
Eric Sunshine 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 not have (so
On Thu, May 21, 2015 at 9:13 AM, Sébastien Guimmara
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
> with
'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
On 05/20/2015 11:39 PM, Ramsay Jones wrote:
On 20/05/15 20:23, Sébastien Guimmara wrote:
Helped-by: Eric Sunshine
Signed-off-by: Ramsay Jones
This should be (at most) 'Helped-by:' - my 'contribution' was
so minor that even a 'Helped-by:' is generous! :-D
ATB,
Ramsay Jones
Ha! I'm still n
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
>
'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
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 wa
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.t
Sébastien Guimmara 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
Eric Sunshine 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, your patch series
karthik nayak 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 unsubscribe from thi
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 "Documentat
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 wh
+++ b/builtin/grep.c
> >>> @@ -738,7 +738,7 @@ int cmd_grep(int argc, const char **argv, const char
> >>> *prefix)
> >>> PARSE_OPT_OPTARG, NULL, (intptr_t)default_pager
> >>> },
> >>> OPT_BOOL(0, "ext-grep&
501 - 600 of 1049 matches
Mail list logo
