a config variable and the user is
made aware 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
On Sun, Mar 22, 2015 at 10:33 AM, Eric Sunshine sunsh...@sunshineco.com wrote:
On Fri, Mar 20, 2015 at 6:36 AM, mdc...@seznam.cz wrote:
I am trying to setup my git ignore (resp. .git/info/exclude) so that I
exclude
all directories and files except the content of directories that I
On Mon, Mar 23, 2015 at 9:00 PM, Duy Nguyen pclo...@gmail.com wrote:
On Sun, Mar 22, 2015 at 10:33 AM, Eric Sunshine sunsh...@sunshineco.com
wrote:
On Fri, Mar 20, 2015 at 6:36 AM, mdc...@seznam.cz wrote:
Any idea what I am doing wrong?
The fourth bullet point of the Pattern Format section
in the description of the idea. It would be great if someone could
point me towards these patches which would help me when I start designing the
details of the unified implementation. Thanks a lot for your time.
Regards,
R Sundararajan.
[1] : http://marc.info/?l=gitm=142666740415816w=2
[2] : http
On Fri, Mar 20, 2015 at 6:36 AM, mdc...@seznam.cz wrote:
I am trying to setup my git ignore (resp. .git/info/exclude) so that I exclude
all directories and files except the content of directories that I
specifically include (incl. anything within them recursively).
I set the
Hello,
I am trying to setup my git ignore (resp. .git/info/exclude) so that I exclude
all directories and files except the content of directories that I
specifically include (incl. anything within them recursively).
I set the .git/info/exclude with the following content:
# Exclude
be great if someone could
point me towards these patches which would help me when I start designing the
details of the unified implementation. Thanks a lot for your time.
Regards,
R Sundararajan.
[1] : http://marc.info/?l=gitm=142666740415816w=2
[2] : http://marc.info/?l=gitm
help me when I start designing the
details of the unified implementation. Thanks a lot for your time.
Regards,
R Sundararajan.
[1] : http://marc.info/?l=gitm=142666740415816w=2
[2] : http://marc.info/?l=gitm=142666773315899w=2
[3] :
http://article.gmane.org/gmane.comp.version-control.git/264966N
it just feels like submodule
would interfere and add more administration overhead on a day to day
basis, affecting productivity.
We do have policies around review etc. With submodules it does
sometimes require engaging owners/reviewers from multiple
repositories. Tools like Gerrit can help
, affecting productivity.
We do have policies around review etc. With submodules it does
sometimes require engaging owners/reviewers from multiple
repositories. Tools like Gerrit can help, particularly where multiple
changes and reviewers are involved.
Is there a third option here I'm missing? If only
to day
basis, affecting productivity.
We do have policies around review etc. With submodules it does
sometimes require engaging owners/reviewers from multiple
repositories. Tools like Gerrit can help, particularly where multiple
changes and reviewers are involved.
Conflicts are definitely going
At my workplace, the team is using Atlassian Stash + git
We have a Core library that is our common code between various
projects. To avoid a single monolithic repository and to allow our
apps and tools to be modularized into their own repos, I have
considered moving Core to a subtree or
with Apple Yosemite
10.10.2. Please help. Thank you very much.
Siamak.
Sent from my iPhone--
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
explaining how this works here, so please read [1] instead, or google
for more updated answers (I don't have a Mac in front of me).
I need to download a version of Git that is compatible with Apple Yosemite
10.10.2. Please help. Thank you very much.
You should be able to use the version of Git
Hi All,
I am a sophomore at Indian Institute of Technology Kanpur and am a GSoC
aspirant for git. Although I have been using git from a long time, this is
the first occasion when I have picked up reading its source code. Can
somebody please help me by telling me how to start off with the above
Sundararajan R dyou...@gmail.com writes:
Although I have been using git from a long time, this is
the first occasion when I have picked up reading its source code. Can
somebody please help me by telling me how to start off with the above
mentioned microproject?
A good place to start
at 1:35 AM, Sundararajan R dyou...@gmail.com wrote:
Hi All,
I am a sophomore at Indian Institute of Technology Kanpur and am a GSoC
aspirant for git. Although I have been using git from a long time, this is
the first occasion when I have picked up reading its source code. Can
somebody please help
On Fri, Feb 27, 2015 at 09:01:58PM +0700, Nguyễn Thái Ngọc Duy wrote:
The current help string is about --no-exclude-standard. But git grep -h
would show --exclude-standard instead. Flip the string. See 0a93fb8
(grep: teach --untracked and --exclude-standard options - 2011-09-27)
for more info
On Wed, Mar 4, 2015 at 6:26 PM, Jeff King p...@peff.net wrote:
It might be nice if parseopt had a PARSE_OPT_NEGHELP option or something
to show the --no- form.
Regardless, yes it would be nice to have something like this. I think
there are places that can make use of this.
Grepping
On Wed, Mar 4, 2015 at 5:16 PM, Jeff King p...@peff.net wrote:
Hmm. If the default is --exclude-standard, then what expect people to
use is --no-exclude-standard. Would it make more sense to list that in
the -h output?
I thought about it and actually edited git-grep man page to clarify
the
On Wed, Mar 04, 2015 at 06:13:32PM +0700, Duy Nguyen wrote:
On Wed, Mar 4, 2015 at 5:16 PM, Jeff King p...@peff.net wrote:
Hmm. If the default is --exclude-standard, then what expect people to
use is --no-exclude-standard. Would it make more sense to list that in
the -h output?
I
The current help string is about --no-exclude-standard. But git grep -h
would show --exclude-standard instead. Flip the string. See 0a93fb8
(grep: teach --untracked and --exclude-standard options - 2011-09-27)
for more info about these options.
Signed-off-by: Nguyễn Thái Ngọc Duy pclo
it is easy to recompile if they
have provided with the details.
Could you please help us to provide additional details for compilation. Thanks
in advance.
Regards,
Ravi.
-Original Message-
From: Ravi Kiran Goud Palpanoori
Sent: Friday, August 01, 2014 5:03 PM
To: 'brian m. carlson'
Cc
and we do so for all HTML documents we
generate, that would be a good change that is not limited to these
places, though.
I've generated a patch for the 'git status --help' that can act as a
reference. (to follow)
For me it's only those pages that have a lone zero that cause problems
due to lack
to be used to
recompile, what parameter settings they need to do, etc. IBM team
told it is easy to recompile if they have provided with the details.
Could you please help us to provide additional details for
compilation. Thanks in advance.
I don't have any more information than this, but I
From: Junio C Hamano gits...@pobox.com
Philip Oakley philipoak...@iee.org writes:
Correct backtick quoting for some of the modification states to give
consistent web rendering.
This is to match the way how XY PATH1 - PATH2 is typeset, I
presume. Some in the body text are already `XY` to
From: Philip Oakley philipoak...@iee.org
From: Junio C Hamano gits...@pobox.com
Philip Oakley philipoak...@iee.org writes:
..
While at it, use 00 for ASCII NUL to avoid any confusion with the
letter O.
(remember its quotation is consumed by ascidoc) looked too much like
an
I
Philip Oakley philipoak...@iee.org writes:
From: Junio C Hamano gits...@pobox.com
Philip Oakley philipoak...@iee.org writes:
Correct backtick quoting for some of the modification states to give
consistent web rendering.
This is to match the way how XY PATH1 - PATH2 is typeset, I
presume.
:
--
Philip
-8
commit 51ec35a196057eae60bb9285c38fb22e49aae1b0
Author: Philip Oakley philipoak...@iee.org
Date: Mon Oct 20 20:21:56 2014 +0100
doc: 'git status' quote the zero (NUL) character
Newer web rendering of 'git status --help --web' shows the zero in
NUL (ASCII 0
Philip Oakley philipoak...@iee.org writes:
From: Junio C Hamano gits...@pobox.com
...
I think it is just the font. I just opened the above page with
Chrome and futzed the text from '0' to '0123456789' to see how it
look. That round thing is consistent with how other digits are
rendered.
Junio C Hamano gits...@pobox.com writes:
Philip Oakley philipoak...@iee.org writes:
From: Junio C Hamano gits...@pobox.com
...
I think it is just the font. I just opened the above page with
Chrome and futzed the text from '0' to '0123456789' to see how it
look. That round thing is
Correct backtick quoting for some of the modification states to give
consistent web rendering.
While at it, use 00 for ASCII NUL to avoid any confusion with the letter O.
Signed-off-by: Philip Oakley philipoak...@iee.org
---
Noticed when reviewing a stackoverflow problem where the OP actually
Philip Oakley philipoak...@iee.org writes:
Correct backtick quoting for some of the modification states to give
consistent web rendering.
This is to match the way how XY PATH1 - PATH2 is typeset, I
presume. Some in the body text are already `XY` to match, but some
others are not, and you are
=tool] [--tool-help] [-y|--no-prompt|--prompt] [file to
merge] ...'
SUBDIRECTORY_OK=Yes
+NONGIT_OK=Yes
OPTIONS_SPEC=
TOOL_MODE=merge
. git-sh-setup
. git-mergetool--lib
-require_work_tree
# Returns true if the mode reflects a symlink
is_symlink () {
@@ -378,6 +378,9
-mergetool.sh
+++ b/git-mergetool.sh
@@ -10,11 +10,11 @@
USAGE='[--tool=tool] [--tool-help] [-y|--no-prompt|--prompt] [file to
merge] ...'
SUBDIRECTORY_OK=Yes
+NONGIT_OK=Yes
OPTIONS_SPEC=
TOOL_MODE=merge
. git-sh-setup
. git-mergetool--lib
-require_work_tree
We cannot rely on the output of `meld --help` when determining
whether or not meld understands the --output option.
Newer versions of meld print a generic help message that does not
mention --output even though it is supported.
Add a mergetool.meld.compat variable to enable the historical
David Aguilar dav...@gmail.com writes:
We cannot rely on the output of `meld --help` when determining
whether or not meld understands the --output option.
Newer versions of meld print a generic help message that does not
mention --output even though it is supported.
This obviously breaks
Junio C Hamano gits...@pobox.com writes:
This obviously breaks those who have happily been using their
installed version of meld that understands and shows --output in the
help text. Is that a minority that is rapidly diminishing?
I would understand it if the change were
changed, 4 insertions(+), 1 deletion(-)
diff --git a/git-mergetool.sh b/git-mergetool.sh
index 96a61ba..cddb533 100755
--- a/git-mergetool.sh
+++ b/git-mergetool.sh
@@ -10,11 +10,11 @@
USAGE='[--tool=tool] [--tool-help] [-y|--no-prompt|--prompt] [file to merge]
...'
SUBDIRECTORY_OK
On Fri, Oct 10, 2014 at 10:01:57AM +0100, Charles Bailey wrote:
On 10 Oct 2014, at 09:51, David Aguilar dav...@gmail.com wrote:
Changes since v1:
NONGIT_OK=Yes was added to make it actually work outside of a git repo.
Does this actually work? The reason that I haven't got around
to
On 11 Oct 2014, at 09:29, David Aguilar dav...@gmail.com wrote:
Thanks for the heads-up.
I tested mergetool and it seems fine but indeed there's an
`if test -e $GIT_DIR/MERGE_RR` in there that is surely not
working as intended.
One solution would be to move the work done in the test
--git a/git-mergetool.sh b/git-mergetool.sh
index 96a61ba..cddb533 100755
--- a/git-mergetool.sh
+++ b/git-mergetool.sh
@@ -10,11 +10,11 @@
USAGE='[--tool=tool] [--tool-help] [-y|--no-prompt|--prompt] [file to merge]
...'
SUBDIRECTORY_OK=Yes
+NONGIT_OK=Yes
OPTIONS_SPEC=
TOOL_MODE=merge
. git
From: Junio C Hamano gits...@pobox.com
Thanks.
Looked alright from a cursory read; I tweaked s/10/-10/ where you
gave examples of limiting output from git log before queuing.
That was my mis-reading. I'd even noticed that it looked 'different'
but just didn't see the leading '-' when checking
(+), 1 deletion(-)
diff --git a/git-mergetool.sh b/git-mergetool.sh
index 96a61ba..a502430 100755
--- a/git-mergetool.sh
+++ b/git-mergetool.sh
@@ -10,11 +10,11 @@
USAGE='[--tool=tool] [--tool-help] [-y|--no-prompt|--prompt] [file to merge]
...'
SUBDIRECTORY_OK=Yes
+NONGIT_OK=Yes
OPTIONS_SPEC
On 10 Oct 2014, at 09:51, David Aguilar dav...@gmail.com wrote:
Changes since v1:
NONGIT_OK=Yes was added to make it actually work outside of a git repo.
Does this actually work? The reason that I haven't got around to resending my
re-roll is that I found that I needed changes to
The Everyday GIT With 20 Commands Or So is not accessible via the
Git help system. Move everyday.txt to giteveryday.txt so that git
help everyday works, and create a new placeholder file everyday.html
to refer people who follow existing URLs to the updated location.
giteveryday.txt now formats
=2005-12-10`, etc.
s/--max-count=//; perhaps?
I've shown both in the update, as it's a help guide. How does it look?
@@ -131,27 +145,34 @@ Clone the upstream and work on it. Feed changes to
upstream.::
$ git clone git://git.kernel.org/pub/scm/.../torvalds/linux-2.6 my2.6
Thanks.
Looked alright from a cursory read; I tweaked s/10/-10/ where you
gave examples of limiting output from git log before queuing.
--
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
The Everyday GIT With 20 Commands Or So is not accessible via the
Git help system. Move everyday.txt to giteveryday.txt so that git
help everyday works, and create a new placeholder file everyday.html
to refer people who follow existing URLs to the updated location.
giteveryday.txt now formats
Here's version three of my patches to make 'git help everyday' work.
It's taken awhile. Previous patches at [1] and [2].
Junio has provided guidance on modernisation of the text, which has
been integrated into patch 1.
Patch 2 regularises the OBSOLETE_HTML method in the make file, in line
Hi Colin,
On 09/08/2014 01:25 PM, Colin Yates wrote:
My understanding is that rebasing branch B onto branch A unrolls all
of branch B's commits and then reduces them onto the HEAD of branch
A.
For example, I took featureA branch from develop three days ago.
develop subsequently had commits
Stefan Beller stefanbel...@gmail.com writes:
We actually want to have the size of one 'name' and not the size
of the names array.
I suspect that the latter is size of a pointer that points at a
cmdname structure, but the original code in help_unknown_cmd() is
wrong. The ones in
Junio C Hamano gits...@pobox.com writes:
Stefan Beller stefanbel...@gmail.com writes:
We actually want to have the size of one 'name' and not the size
of the names array.
...
I suspect that the latter is size of a pointer that points at a
cmdname structure, but the original code in
We actually want to have the size of one 'name' and not the size
of the names array.
Signed-off-by: Stefan Beller stefanbel...@gmail.com
---
help.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/help.c b/help.c
index 7af65e2..2072a87 100644
--- a/help.c
+++ b/help.c
@@
On Sat, Sep 13, 2014 at 10:23:03PM -0700, Junio C Hamano wrote:
On Sat, Sep 13, 2014 at 7:00 PM, Perry Hutchison per...@pluto.rain.com
wrote:
David Aguilar dav...@gmail.com wrote:
Add a #ifndef guard to ensure that common-cmds.h can only
be included by help.c.
This strikes me as a
Junio C Hamano gits...@pobox.com wrote:
On Sat, Sep 13, 2014 at 7:00 PM, Perry Hutchison per...@pluto.rain.com
wrote:
David Aguilar dav...@gmail.com wrote:
Add a #ifndef guard to ensure that common-cmds.h can only
be included by help.c.
... If these definitions are intended to be
On Sun, Sep 14, 2014 at 12:55:41AM -0700, Perry Hutchison wrote:
Junio C Hamano gits...@pobox.com wrote:
On Sat, Sep 13, 2014 at 7:00 PM, Perry Hutchison per...@pluto.rain.com
wrote:
David Aguilar dav...@gmail.com wrote:
Add a #ifndef guard to ensure that common-cmds.h can only
be
cmdname_help {
char name[16];
char help[80];
diff --git a/help.c b/help.c
index 7af65e2..abf1689 100644
--- a/help.c
+++ b/help.c
@@ -3,11 +3,12 @@
#include exec_cmd.h
#include levenshtein.h
#include help.h
-#include common-cmds.h
#include string-list.h
#include column.h
#include
David Aguilar dav...@gmail.com wrote:
Add a #ifndef guard to ensure that common-cmds.h can only
be included by help.c.
This strikes me as a very peculiar, and sub-optimal, way of
achieving the purpose. If these definitions are intended to
be private to help.c, why not put them there and
On Sat, Sep 13, 2014 at 7:00 PM, Perry Hutchison per...@pluto.rain.com wrote:
David Aguilar dav...@gmail.com wrote:
Add a #ifndef guard to ensure that common-cmds.h can only
be included by help.c.
This strikes me as a very peculiar, and sub-optimal, way of
achieving the purpose. If these
Hi all,
TLDR; I am seeing merge conflicts when rebasing even though applying
them to HEAD of target branch should work. Can you please upgrade my
understanding so I understand.
My understanding is that rebasing branch B onto branch A unrolls all
of branch B's commits and then reduces them onto
Am 08.09.2014 13:25, schrieb Colin Yates:
For example, let's imagine that #f1 removed fileA, some time later #d1
Assumption: #d1 is in the branch you call develop HEAD.
added a line to that file. If I was doing a merge then of course this
should be a conflict, however applying #f1 to develop
. To find this out, we are conducting an Online Survey for
Software Developers. From the results we expect new insights into
debugging practice that help us to suggest new directions for future
research. So if you are a software developer or know any software
developers, you can really help us
Hi,
I am writing below couple of questions. If it is not the right place to ask
please ignore and suggest me what to do to get the help on these questions.
1) What version of SSL is supported by GIT 1.8.3 or GIT 1.9.0
2) I have installed git 1.8.3 in AIX server 6.1 TL8 SP2. It worked fine
of questions. If it is not the right place to ask
please ignore and suggest me what to do to get the help on these questions.
1) What version of SSL is supported by GIT 1.8.3 or GIT 1.9.0
2) I have installed git 1.8.3 in AIX server 6.1 TL8 SP2. It worked fine and
able to extract code from git
On Fri, Aug 01, 2014 at 07:30:11PM +, ravikirangoud_palpano...@vfc.com
wrote:
Hi,
I am writing below couple of questions. If it is not the right place
to ask please ignore and suggest me what to do to get the help on
these questions.
1) What version of SSL is supported by GIT 1.8.3
Subject: Re: Git Help needed
This looks more like a packaging/build issue than a git issue.
It looks like whomever built your version of git built it against a specific
version of the OpenSSL library.
You should probably contact the folks that built your binary and ask them to
update and build
, August 01, 2014 4:05 PM
To: Ravi Kiran Goud Palpanoori
Cc: git@vger.kernel.org
Subject: Re: Git Help needed
On Fri, Aug 01, 2014 at 07:30:11PM +, ravikirangoud_palpano...@vfc.com
wrote:
Hi,
I am writing below couple of questions. If it is not the right place
to ask please ignore
On Fri, Aug 01, 2014 at 08:27:24PM +, ravikirangoud_palpano...@vfc.com
wrote:
Hi brian,
Thanks for your quick reply.
I downloaded git 1.9.0 from the site
https://code.google.com/p/git-core/downloads/list.
That URL is obsolete. Try https://www.kernel.org/pub/software/scm/git/
Google
Help needed
On Fri, Aug 01, 2014 at 08:27:24PM +, ravikirangoud_palpano...@vfc.com
wrote:
Hi brian,
Thanks for your quick reply.
I downloaded git 1.9.0 from the site
https://code.google.com/p/git-core/downloads/list.
That URL is obsolete. Try https://www.kernel.org/pub/software/scm/git
From: Charles Bailey cbaile...@bloomberg.net
Signed-off-by: Charles Bailey cbaile...@bloomberg.net
---
You can call git difftool --tool-help outside of a work tree but not
mergetool --tool-help but there's not real reason for this restriction
and it can be easily relaxed by deferring
to syslog. By default messages will be sent.
+.TP
+.BI \-Q
+Do not print messages to standard output. By default messages will be printed.
+.TP
+.BI \-h
+Display a help message.
+.TP
+.B \-v
+Prints the software version and exits.
+
+.SH COMMANDS
+
+.B phc_ctl
+is controlled by passing commands which
Jacob Keller jacob.e.kel...@intel.com writes:
This is an updated version of a script I wrote a couple years ago for
I suspect that this is not for us ;-)
--
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
On Thu, 2014-07-10 at 16:20 -0700, Junio C Hamano wrote:
Jacob Keller jacob.e.kel...@intel.com writes:
This is an updated version of a script I wrote a couple years ago for
I suspect that this is not for us ;-)
--
To unsubscribe from this list: send the line unsubscribe git in
the body
. Merge the remote changes (e.g. 'git pull')
hint: before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.
Obviously I have already made the pull command (as suggested in the message)
and it says to me
that everything is up to date.
On SO there is the very same
Option explanation is in rev-list-options.txt. The interaction with -z
is left undecided.
Signed-off-by: Nguyễn Thái Ngọc Duy pclo...@gmail.com
---
On Fri, Mar 21, 2014 at 2:15 AM, Junio C Hamano gits...@pobox.com wrote:
* Get rid of saved_linear, use another flag in struct object instead
Nguyễn Thái Ngọc Duy pclo...@gmail.com writes:
Option explanation is in rev-list-options.txt. The interaction with -z
is left undecided.
Signed-off-by: Nguyễn Thái Ngọc Duy pclo...@gmail.com
---
On Fri, Mar 21, 2014 at 2:15 AM, Junio C Hamano gits...@pobox.com wrote:
* Get rid of
Nguyễn Thái Ngọc Duy pclo...@gmail.com writes:
Option explanation is in rev-list-options.txt. The interaction with -z
is left undecided.
Signed-off-by: Nguyễn Thái Ngọc Duy pclo...@gmail.com
---
Thanks.
* Revert back to the old option name --show-linear-break
* Get rid of
On Fri, Mar 21, 2014 at 2:15 AM, Junio C Hamano gits...@pobox.com wrote:
* Get rid of saved_linear, use another flag in struct object instead
I cannot offhand say if I like this change or not. A flag bit is a
scarce and limited resource; commit slabs felt more suited for
implementation of
Option explanation is in rev-list-options.txt. The interaction with -z
is left undecided.
Signed-off-by: Nguyễn Thái Ngọc Duy pclo...@gmail.com
---
* Revert back to the old option name --show-linear-break
* Get rid of saved_linear, use another flag in struct object instead
* Fix not showing
Signed-off-by: Nguyễn Thái Ngọc Duy pclo...@gmail.com
---
v2 renames the option name to --nonlinear-barrier and fixes using it
with --dense. Best used with --no-merges to see patch series.
Documentation/rev-list-options.txt | 7 ++
log-tree.c | 4 +++
revision.c
On Mon, Mar 17, 2014 at 8:51 AM, Nguyễn Thái Ngọc Duy pclo...@gmail.com wrote:
Signed-off-by: Nguyễn Thái Ngọc Duy pclo...@gmail.com
---
v2 renames the option name to --nonlinear-barrier and fixes using it
with --dense. Best used with --no-merges to see patch series.
wondered if the saved-parents slab we already have can be
easily reused for this, but it probably would not help.
I do not quite understand the if we do not have previous parents
bit, though. Is it meant to trigger only at the very beginning?
Thanks.
--
To unsubscribe from this list: send the line
please help me with the memory allacation and
strbuf_release()
Thanks,
--sai krishna
--
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
+0xed)[0x2b5f3b4e376d]
/home/saikrishna/Desktop/libcloud-0.14.1/sai/git/git[0x405109]
Can some one please help me with the memory allacation and strbuf_release()
Read the microproject text carefully and _fully_. It provides the clue
you need to understand the problem.
Rewrite bulk
Joel Nothman joel.noth...@gmail.com writes:
Git help --all had listed all git commands, but no configured aliases.
This includes aliases as a separate listing, after commands in the main
git directory and other $PATH directories.
... and why is this a good thing?
Signed-off-by: Joel
On 26 February 2014 06:15, Junio C Hamano gits...@pobox.com wrote:
Joel Nothman joel.noth...@gmail.com writes:
Git help --all had listed all git commands, but no configured aliases.
This includes aliases as a separate listing, after commands in the main
git directory and other $PATH
Joel Nothman joel.noth...@gmail.com writes:
arguments to git help. They are also like commands in that it is
possible to forget their name, or whether they are defined on a
particular workstation, and to hence want a listing.
I did envision that it would be useful for the last case
On 26 February 2014 08:51, Junio C Hamano gits...@pobox.com wrote:
Joel Nothman joel.noth...@gmail.com writes:
arguments to git help. They are also like commands in that it is
possible to forget their name, or whether they are defined on a
particular workstation, and to hence want a listing
From: Joel Nothman joel.noth...@gmail.com
On 26 February 2014 06:15, Junio C Hamano gits...@pobox.com wrote:
Joel Nothman joel.noth...@gmail.com writes:
Git help --all had listed all git commands, but no configured
aliases.
This includes aliases as a separate listing, after commands
Joel Nothman joel.noth...@gmail.com writes:
Git help --all had listed all git commands, but no configured aliases.
This includes aliases as a separate listing, after commands in the main
git directory and other $PATH directories.
Signed-off-by: Joel Nothman joel.nothman at gmail.com
Git help --all had listed all git commands, but no configured aliases.
This includes aliases as a separate listing, after commands in the main
git directory and other $PATH directories.
Signed-off-by: Joel Nothman joel.nothman at gmail.com
---
Documentation/git-help.txt | 4 +--
builtin/help.c
+
+gituser-manual - a link to the user-manual docbook
+
+
+SYNOPSIS
+
+[verse]
+'git help user-manual'
+
+link:user-manual.html[Git User's Manual]
Is it just me, or is typing
$ git help user-manual
and not seeing the manual itself, but only a link you have to click
(7)
+=
+
+NAME
+
+gituser-manual - a link to the user-manual docbook
+
+
+SYNOPSIS
+
+[verse]
+'git help user-manual'
+
+link:user-manual.html[Git User's Manual]
Is it just me, or is typing
$ git help user-manual
and not seeing the manual itself, but only a link you
@@
+gituser-manual(7)
+=
+
+NAME
+
+gituser-manual - a link to the user-manual docbook
+
+
+SYNOPSIS
+
+[verse]
+'git help user-manual'
+
+link:user-manual.html[Git User's Manual]
+
+DESCRIPTION
+---
+Git is a fast, scalable, distributed revision control system
Signed-off-by: Nguyễn Thái Ngọc Duy pclo...@gmail.com
---
This is a more serious attempt to make non-linear history more
visible without --graph. It looks like this
commit e4ddb05720710213108cd13ddd5a115e12a6211d
Author: Andy Spencer andy753...@gmail.com
within the
git(1) section it came from, and a new release-notes(7) man page.
With that set up the Documentation/Makefile would generate the man
pages, with their appropriate links, which can be accessed via the 'git
help' command.
The big 'however' was that this would not actually include
From: Stefan Näwe stefan.na...@atlas-elektronik.com
Am 16.01.2014 22:14, schrieb Philip Oakley:
From: Stefan Näwe stefan.na...@atlas-elektronik.com
[...]
I'd really like to see 'git help relnotes' working as well...
Stefan
Stefan,
Were you thinking that all the release notes would
Philip Oakley philipoak...@iee.org writes:
Determining which is the current release note is possibly more
problematic, which should be when making the documentation.
Hmmm Why?
You are already aware of the stale-notes section, no? Isn't the top
one the latest?
--
To unsubscribe from this
the latest?
It's that the 'git help release-notes' would _include_ the latest
release notes, not just link to them (which is what the stalenotes
currently does). Or at least that was the idea.
Trying to determine the latest version, and then include those release
notes, and the subsequent
501 - 600 of 959 matches
Mail list logo
