Joel Nothman 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 Not
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 gmail.com>
---
Documentation/git-help.txt | 4 +--
builtin/hel
==
+
+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 hav
===
> +
> +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 us
)
+=
+
+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 with an
+unusual
Signed-off-by: Nguyễn Thái Ngọc Duy
---
This is a more serious attempt to make non-linear history more
visible without --graph. It looks like this
commit e4ddb05720710213108cd13ddd5a115e12a6211d
Author: Andy Spencer
tree_entry_interesting: match against all pathspecs
luded both 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 thi
"Philip Oakley" writes:
> I already have a local patch that creates a stalenote.txt file, and
> includes that in a "release-notes(7)" man page, but it still leaves
> the actual release notes in a separate plain text file, linked from
> the man page, rather than being right at hand, which is what
est?
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 s
"Philip Oakley" 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 list: send the l
From: "Stefan Näwe"
Am 16.01.2014 22:14, schrieb Philip Oakley:
From: "Stefan Näwe"
[...]
I'd really like to see 'git help relnotes' working as well...
Stefan
Stefan,
Were you thinking that all the release notes would be quoted verbatim
in
the one lo
Am 16.01.2014 22:14, schrieb Philip Oakley:
> From: "Stefan Näwe"
> [...]
>>
>> I'd really like to see 'git help relnotes' working as well...
>>
>> Stefan
>
> Stefan,
>
> Were you thinking that all the release notes would be qu
From: "Stefan Näwe"
[...]
I'd really like to see 'git help relnotes' working as well...
Stefan
Stefan,
Were you thinking that all the release notes would be quoted verbatim in
the one long man page?
Or that it would be a set of links to each of the individual t
Signed-off-by: David Aguilar
---
git-pull.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/git-pull.sh b/git-pull.sh
index 7dbf6b1..68b2e40 100755
--- a/git-pull.sh
+++ b/git-pull.sh
@@ -4,7 +4,7 @@
#
# Fetch one or more remote refs and merge it/them into the current HEAD.
)
+=
+
+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 with an
+unusual
The "Everyday GIT With 20 Commands Or So" is not accessible via the
Git help system. Fix that.
Move everyday.txt to giteveryday.txt.
Update giteveryday.txt to fit man page formatting.
Add standard man page section titles.
Also adjust anchor text markup for man page format.
Add gitevery
From: "Junio C Hamano"
"Philip Oakley" writes:
From: "Junio C Hamano"
I think we already use a nicer way to set up a page alias to keep
old links working than making a copy in Documentation/; please mimic
that if possible.
This was mainly about ensuring tha
From: "Junio C Hamano"
"Philip Oakley" writes:
From: "Junio C Hamano"
I think we already use a nicer way to set up a page alias to keep
old links working than making a copy in Documentation/; please mimic
that if possible.
This was mainly about ensuring tha
Hi,
Philip Oakley wrote:
> The "Everyday GIT With 20 Commands Or So" guide is not accessible
> via the git help system. Fix that.
Neat. :)
Junio covered everything I'd want to say about patch 1/6.
After fixing that, I'd suggest squashing all 6 patches into a single
"Philip Oakley" writes:
> From: "Junio C Hamano"
>>I think we already use a nicer way to set up a page alias to keep
>> old links working than making a copy in Documentation/; please mimic
>> that if possible.
>
> This was mainly about ensuring t
ommands,
> as things have vastly changed over the past 8 years. Perhaps we
> should do that after reorganizing with something like this series.
I'd really like to see 'git help relnotes' working as well...
Stefan
--
-
From: "Junio C Hamano"
I think we already use a nicer way to set up a page alias to keep
old links working than making a copy in Documentation/; please mimic
that if possible.
This was mainly about ensuring that the 'git help' command could access
these extra extra guid
I think we already use a nicer way to set up a page alias to keep
old links working than making a copy in Documentation/; please mimic
that if possible.
It may be overdue to refresh the suggested set of "top 20" commands,
as things have vastly changed over the past 8 years. Perhaps we
should do t
Signed-off-by: Philip Oakley
---
builtin/help.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/builtin/help.c b/builtin/help.c
index cc17e67..45509ce 100644
--- a/builtin/help.c
+++ b/builtin/help.c
@@ -418,6 +418,7 @@ static struct {
const char *help;
} common_guides
The "Everyday GIT With 20 Commands Or So" guide is not accessible via the git
help system. Fix that.
The git everyday file does not use the appropriate filenaming convention for
help files, and is not suitably formatted for display as a man page.
First copy everyday.txt to gitev
It's hard to tell which author conversion test failed when the email
addresses look similar.
Signed-off-by: Richard Hansen
Reviewed-by: Felipe Contreras
---
contrib/remote-helpers/test-hg.sh | 20 ++--
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/contrib/remot
It's hard to tell which author conversion test failed when the email
addresses look similar.
Signed-off-by: Richard Hansen
---
contrib/remote-helpers/test-hg.sh | 20 ++--
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/contrib/remote-helpers/test-hg.sh
b/contrib
On 2013-11-11 14:29, Felipe Contreras wrote:
> On Mon, Nov 11, 2013 at 1:19 PM, Richard Hansen wrote:
>> On 2013-11-11 06:42, Felipe Contreras wrote:
>>> Richard Hansen wrote:
It's hard to tell which author conversion test failed when the email
addresses look similar.
Signed-of
On Mon, Nov 11, 2013 at 1:19 PM, Richard Hansen wrote:
> On 2013-11-11 06:42, Felipe Contreras wrote:
>> Richard Hansen wrote:
>>> It's hard to tell which author conversion test failed when the email
>>> addresses look similar.
>>>
>>> Signed-off-by: Richard Hansen
>>> ---
>>> contrib/remote-hel
On 2013-11-11 06:42, Felipe Contreras wrote:
> Richard Hansen wrote:
>> It's hard to tell which author conversion test failed when the email
>> addresses look similar.
>>
>> Signed-off-by: Richard Hansen
>> ---
>> contrib/remote-helpers/test-hg.sh | 20 ++--
>> 1 file changed, 10
Richard Hansen wrote:
> It's hard to tell which author conversion test failed when the email
> addresses look similar.
>
> Signed-off-by: Richard Hansen
> ---
> contrib/remote-helpers/test-hg.sh | 20 ++--
> 1 file changed, 10 insertions(+), 10 deletions(-)
>
> diff --git a/cont
It's hard to tell which author conversion test failed when the email
addresses look similar.
Signed-off-by: Richard Hansen
---
contrib/remote-helpers/test-hg.sh | 20 ++--
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/contrib/remote-helpers/test-hg.sh
b/contrib
Signed-off-by: Christian Couder
---
help.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/help.c b/help.c
index f068925..b41d2d5 100644
--- a/help.c
+++ b/help.c
@@ -148,7 +148,7 @@ static void list_commands_in_dir(struct cmdnames *cmds,
while ((de = readdir(d
n."));
}
@@ -258,7 +258,7 @@ static int add_man_viewer_info(const char *var, const char
*value)
static int git_help_config(const char *var, const char *value, void *cb)
{
- if (!prefixcmp(var, "column."))
+ if (has_prefix(var, "column."))
On Thu, Oct 31, 2013 at 3:41 PM, Junio C Hamano wrote:
> Eugene Sajine writes:
>
>> One note: i tried the ${GIT_PREFIX:-.} and ${GIT_PREFIX} and it seems
>> to give the same results. What is the expected difference here?
>
> GIT_PREFIX may be an empty string when you run from the top-level,
> in
Eugene Sajine writes:
> One note: i tried the ${GIT_PREFIX:-.} and ${GIT_PREFIX} and it seems
> to give the same results. What is the expected difference here?
GIT_PREFIX may be an empty string when you run from the top-level,
in which case you would end up with "cd && ..." and end up working
i
On Thu, Oct 31, 2013 at 2:15 PM, David Aguilar wrote:
> On Thu, Oct 31, 2013 at 11:07:19AM -0700, Junio C Hamano wrote:
>> David Aguilar writes:
>>
>> > A-ha.. I think adding the chdir to alias is possible using a function.
>>
>> You do not have to use a function to do so, no?
>
> Right, of cours
On Thu, Oct 31, 2013 at 11:07:19AM -0700, Junio C Hamano wrote:
> David Aguilar writes:
>
> > A-ha.. I think adding the chdir to alias is possible using a function.
>
> You do not have to use a function to do so, no?
Right, of course.
So something like:
[alias]
example = "!cd ${GIT_PR
David Aguilar writes:
> A-ha.. I think adding the chdir to alias is possible using a function.
You do not have to use a function to do so, no?
--
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://vg
uired pathnames:
>
> when i'm in a subfolder in git repo i can say
>
> git log filename
>
> But it seems that if the alias is used i need to specify full path
> from the root of the repo no matter where i am.
>
> git log a/b/c/filename
>
> the difference is obv
e is some difference between the
required pathnames:
when i'm in a subfolder in git repo i can say
git log filename
But it seems that if the alias is used i need to specify full path
from the root of the repo no matter where i am.
git log a/b/c/filename
the difference is obviously in the
Eugene Sajine writes:
> That was my initial intention, because I would like to be able to pass
> parameters like to git log or git blame correctly without the explicit
> use of $1. Could you please advise about how to make it work with the
> !sh -c ?
>
> Because the same exact (sed 's/@\\S*//') s
On Wed, Oct 30, 2013 at 5:02 PM, Junio C Hamano wrote:
> Eugene Sajine writes:
>
>> On Wed, Oct 30, 2013 at 3:57 PM, Ralf Thielow wrote:
>>> lg=!git log --pretty=format:'%h %ad %ae %s' --date=short | sed 's/@\\S*//g'
>>>
>>> should work.
>>
>>
>> It did! thanks! I didn't know that "!sh -c" is no
Eugene Sajine writes:
> On Wed, Oct 30, 2013 at 3:57 PM, Ralf Thielow wrote:
>> lg=!git log --pretty=format:'%h %ad %ae %s' --date=short | sed 's/@\\S*//g'
>>
>> should work.
>
>
> It did! thanks! I didn't know that "!sh -c" is not needed
"sh -c" is often used when you pass arguments to your sc
On Wed, Oct 30, 2013 at 3:57 PM, Ralf Thielow wrote:
> lg=!git log --pretty=format:'%h %ad %ae %s' --date=short | sed 's/@\\S*//g'
>
> should work.
It did! thanks! I didn't know that "!sh -c" is not needed
>
> On Wed, Oct 30, 2013 at 8:34 PM, Eugene Sajine wrote:
>> Hi,
>>
>> I need some advic
lg=!git log --pretty=format:'%h %ad %ae %s' --date=short | sed 's/@\\S*//g'
should work.
On Wed, Oct 30, 2013 at 8:34 PM, Eugene Sajine wrote:
> Hi,
>
> I need some advice about creating the git command alias:
>
> I have this as the command:
>
> git log --pretty=format:"%h %ad %ae %s" --date=sho
On Wed, Oct 30, 2013 at 3:47 PM, Andrew Ardill wrote:
> Have you tried backslash escaping the backslash? double escaping?
>
> I don't know how many are required, but I would try first \S, then
> \\S, then S, etc
> Regards,
>
> Andrew Ardill
When i do that it stops understanding \S* as regexp
Have you tried backslash escaping the backslash? double escaping?
I don't know how many are required, but I would try first \S, then
\\S, then S, etc
Regards,
Andrew Ardill
On 30 October 2013 12:34, Eugene Sajine wrote:
> Hi,
>
> I need some advice about creating the git command alias:
>
>
Hi,
I need some advice about creating the git command alias:
I have this as the command:
git log --pretty=format:"%h %ad %ae %s" --date=short | sed 's/@\S*//g'
The purpose is to cut off the email domain and keep only username.
I'm trying to create this as the alias:
lg = !sh -c 'git log --p
On Fri, Oct 4, 2013 at 7:34 AM, Stefan Saasen wrote:
> The help text for the `tool` flag should mention:
>
> --tool=
>
> instead of:
>
> --tool-
>
> Signed-off-by: Stefan Saasen
> ---
Good eyes!
Reviewed-by: David Aguilar
Thanks
> git-mergetool--l
The help text for the `tool` flag should mention:
--tool=
instead of:
--tool-
Signed-off-by: Stefan Saasen
---
git-mergetool--lib.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/git-mergetool--lib.sh b/git-mergetool--lib.sh
index feee6a4..e1c7eb1 100644
--- a
I am Mrs, Nancy Butler. I have a foundation/Estate uncompleted {worth sum of
USD 4,142,728.00 Dollars} and need somebody to help me finish it because of my
health. Contact me with this email (
nancybutler...@yahoo.co.uk<mailto:nancybutler...@yahoo.co.uk> ).
--
To unsubscribe from thi
oblem to solve is the actual tree
> "deltification". I don't have the time to spend on this otherwise very
> interesting problem (IMHO at least) so I'm sending this request for help
> in the hope that more people would be keen to contribute their computing
> skills
o spend on this otherwise very
interesting problem (IMHO at least) so I'm sending this request for help
in the hope that more people would be keen to contribute their computing
skills to solve this challenge.
I'll make a quick description of the pv4 tree encoding first and expl
The search help link was a superscript question mark right next to
a drop-down menu, which looks misaligned and is a cramped and
awkward click target. Remove the superscript tags and add some
spacing to fix these nits. Add a title attribute to provide an
explanatory mouseover.
Signed-off-by: Tony
things, but I always seem to either get the "sparse checkout
> leaves no entry on working directory" error or no effect at all. In the end,
> I basically just don't really understand how this file is supposed to work,
> so I'd rather get some expert help here rather than
no
entry on working directory" error or no effect at all. In the end, I basically
just don't really understand how this file is supposed to work, so I'd rather
get some expert help here rather than thrashing about randomly. I realize that
sparse checkouts is usually used to sele
Jakub Narębski wrote:
> > - -values => ['commit', 'grep', 'author',
> > 'committer', 'pickaxe']) .
> > + -values => ['commit', 'grep', 'author',
> > 'committer', 'pickaxe']) .
>
> Nb. what changed here (in line above)?
Whoops, tab damag
On Tue, Jul 9, 2013 at 7:15 PM, Tony Finch wrote:
> The search help link was a superscript question mark right next to
> a drop-down menu, which looks misaligned
I think the idea was to simulate footnote explaining search terms
(I think, I am not the author of this f
Al 30/07/13 11:58, En/na Fredrik Gustafsson ha escrit:
Git subtree is very convenient to get all the sub-projects into the
main-project directory tree
and to send back sub-project commits to the corresponding repository.
But I don't understand the work flow very well.
I haven't used subtree tha
On Tue, Jul 30, 2013 at 11:32:22AM +0200, Gabriel Jover wrote:
> Dear all,
>
> I am trying to avoid using git submodules and thus I am testing if
> git subtree fit my needs.
> I have a set of sub-projects linked to a main-project.
Just out of curiosity, why are you trying to avoid submodules?
>
Dear all,
I am trying to avoid using git submodules and thus I am testing if git
subtree fit my needs.
I have a set of sub-projects linked to a main-project.
Git subtree is very convenient to get all the sub-projects into the
main-project directory tree
and to send back sub-project commits t
This is an extension of c6807a4 (clone: open a shortcut for
connectivity check - 2013-05-26) to reduce the cost of connectivity
check at clone time, this time with smart http protocol.
Signed-off-by: Nguyễn Thái Ngọc Duy
---
Documentation/git-fetch-pack.txt| 4
Documentation/gitremote-
The search help link was a superscript question mark right next to
a drop-down menu, which looks misaligned and is a cramped and
awkward click target. Remove the superscript tags and add some
spacing to fix these nits. Add a title attribute to provide an
explanatory mouseover.
Signed-off-by: Tony
Stefano Lattarini writes:
> The configure option to disable threading is '--disable-pthreads',
> not '--without-pthreads'.
>
> Signed-off-by: Stefano Lattarini
> ---
Thanks.
> configure.ac | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/configure.ac b/configure.ac
> i
The configure option to disable threading is '--disable-pthreads',
not '--without-pthreads'.
Signed-off-by: Stefano Lattarini
---
configure.ac | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/configure.ac b/configure.ac
index f3462d9..2f43393 100644
--- a/configure.ac
+++ b/co
Junio C Hamano writes:
> Ramkumar Ramachandra writes:
>
>> Junio C Hamano wrote:
$ ~/src/git
error: object file
.git/objects/8e/6a6dda24b017915449897fcc1353a9b848fd2f is empty
error: object file
.git/objects/8e/6a6dda24b017915449897fcc1353a9b848fd2f is empty
John Keeping wrote:
> Would it be nicer to pass a string in here instead of a flag? Then this
> becomes:
>
> strbuf_addf(&man_page, "(%s \"%s\")", command, page);
>
> You should probably also rename this function to "exec_emacsclient" or
> something as well now that it doesn't just launch
On Sat, Jun 22, 2013 at 05:13:29PM +0530, Ramkumar Ramachandra wrote:
> Corresponding to woman.
>
> Signed-off-by: Ramkumar Ramachandra
> ---
> Documentation/git-help.txt | 3 +++
> builtin/help.c | 11 ---
> 2 files changed, 11 insertions(+), 3 deletions(-)
>
> diff --git
Corresponding to woman.
Signed-off-by: Ramkumar Ramachandra
---
Documentation/git-help.txt | 3 +++
builtin/help.c | 11 ---
2 files changed, 11 insertions(+), 3 deletions(-)
diff --git a/Documentation/git-help.txt b/Documentation/git-help.txt
index b21e9d7..0cb4c46 100644
Junio C Hamano wrote:
> A tl;dr is that we _trust_ our refs and everything reachable from
> them has to be complete. If that is not the case, things will not
> work, and it is not a priority to add workarounds in the normal
> codepath to slow things down.
Makes sense.
> That does not forbid an a
Ramkumar Ramachandra writes:
> Junio C Hamano wrote:
>>> $ ~/src/git
>>> error: object file
>>> .git/objects/8e/6a6dda24b017915449897fcc1353a9b848fd2f is empty
>>> error: object file
>>> .git/objects/8e/6a6dda24b017915449897fcc1353a9b848fd2f is empty
>>> fatal: loose object 8e6a6dda24b017
Junio C Hamano wrote:
>> $ ~/src/git
>> error: object file
>> .git/objects/8e/6a6dda24b017915449897fcc1353a9b848fd2f is empty
>> error: object file
>> .git/objects/8e/6a6dda24b017915449897fcc1353a9b848fd2f is empty
>> fatal: loose object 8e6a6dda24b017915449897fcc1353a9b848fd2f (stored
>> i
Ramkumar Ramachandra writes:
> $ ~/src/git
> error: object file
> .git/objects/8e/6a6dda24b017915449897fcc1353a9b848fd2f is empty
> error: object file
> .git/objects/8e/6a6dda24b017915449897fcc1353a9b848fd2f is empty
> fatal: loose object 8e6a6dda24b017915449897fcc1353a9b848fd2f (stored
>
06658278b871a6e2ca66694efcadacca is empty
fatal: loose object 64fa33d706658278b871a6e2ca66694efcadacca (stored
in .git/objects/64/fa33d706658278b871a6e2ca66694efcadacca) is corrupt
error: github.com:artagnon/git did not send all necessary objects
Auto packing the repository for optimum performan
From: Junio C Hamano
b397ea (status: show more info than "currently not on any branch",
2013-03-13) wanted to make sure that after a checkout to detach HEAD,
the user can see where the HEAD was originally detached from. The last
test added by that commit to t/status-help shows o
From: Junio C Hamano
b397ea (status: show more info than "currently not on any branch",
2013-03-13) wanted to make sure that after a checkout to detach HEAD,
the user can see where the HEAD was originally detached from. The last
test added by that commit to t/status-help shows o
From: Junio C Hamano
b397ea (status: show more info than "currently not on any branch",
2013-03-13) wanted to make sure that after a checkout to detach HEAD,
the user can see where the HEAD was originally detached from. The last
test added by that commit to t/status-help shows o
; I don't mean a setenv() kind of thing: how would we unset it after
>> that? Perhaps something like execvpe(), passing in the environment as
>> an argument?
Running "man" is the last thing we do before exitting "git help" and
exec_man_man() does seem to do ex
;s because they want a specific pager
when reading man pages - invoking man through "git help" shouldn't cause
it to behave differently in this case.
--
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
Matthieu Moy wrote:
> I find it a bit weird that Git sets the configuration for external
> commands, but it may make sense. No strong opinion here.
I don't mean a setenv() kind of thing: how would we unset it after
that? Perhaps something like execvpe(), passing in the environment as
an argument?
a small problem with it
> though: why is there no option for Emacs man corresponding to Emacs
> woman?
I guess because no one implemented it ;-).
>> I personally run M-x git-foo RET, and never run "git help".
>
> M-x man git-foo RET, you mean?
Yes, sorry.
--
Mat
Matthieu Moy wrote:
> Michael Campbell writes:
>> I have my global git config pager set to 'cat', but when I do a "git
>> help ", it still uses a pager. This is especially irksome in
>> emacs shell buffers, where I am most of the time. I know I can do a
Michael Campbell writes:
> I have my global git config pager set to 'cat', but when I do a "git
> help ", it still uses a pager. This is especially irksome in
> emacs shell buffers, where I am most of the time. I know I can do a
> M-x man -> git-, but wondere
I have my global git config pager set to 'cat', but when I do a "git
help ", it still uses a pager. This is especially irksome in
emacs shell buffers, where I am most of the time. I know I can do a
M-x man -> git-, but wondered if this was a bug or user
error. ("gi
On 2013-05-21 02:59, Quilkey, Tony wrote:
Hi,
I am looking at formulating and then documenting our vcs workflow
using Git at work. I have an idea of how I want things to work, but am
a little hazy on some of the details.
Our basic workflow will be based around:
http://nvie.com/posts/a-successfu
On Monday, May 20, 2013 at 20:59 EDT,
"Quilkey, Tony" wrote:
> I am looking at formulating and then documenting our vcs workflow
> using Git at work. I have an idea of how I want things to work, but am
> a little hazy on some of the details.
>
> Our basic workflow will be based around:
> ht
On Tue, May 21, 2013 at 10:59:17AM +1000, Quilkey, Tony wrote:
> I am looking at formulating and then documenting our vcs workflow
> using Git at work. I have an idea of how I want things to work, but am
> a little hazy on some of the details.
>
> Our basic workflow will be based around:
> http://
Hi,
I am looking at formulating and then documenting our vcs workflow
using Git at work. I have an idea of how I want things to work, but am
a little hazy on some of the details.
Our basic workflow will be based around:
http://nvie.com/posts/a-successful-git-branching-model, with a few
exceptions
Hi,
This topic is based on the rebase.autostash topic. It cleans up a few
things, introduces 'git stash store', and patches rebase to use it.
Should be simple enough.
Thanks.
Ramkumar Ramachandra (6):
Documentation/stash: correct synopsis for create
Documentation/stash: document short form
On Thursday 09 May 2013 04:19 AM, Junio C Hamano wrote:
> [...] which in turn made me realize that some commands may not even know
> if the user mistyped a ref. It is not an objection to this patch
> per-se, but a useful future enhancement may be to allow the callers
> call guess_mistyped_ref() d
Vikrant Varma writes:
> When a ref is not known, currently functions call die() with an
> error message.
The first part read somewhat awkward, so I started rewriting the
above like so:
When the user gives an unknown string to a command that expects
to see a ref, we could be more helpful
com/An-individual-Learn-how-to-Help-make-pandora-sale-tp7585097.html
Sent from the git mailing list archive at Nabble.com.
--
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
When a ref is not known, currently functions call die() with an error message.
Add helper function help_unknown_ref to take care of displaying an error
message along with a list of suggested refs the user might have meant.
Example:
$ git merge foo
merge: foo - not something we can
stake that the code
>> you need to add to 'git merge' would encounter and could help
>> the user with.
>
> Yes. I like your suggestion of using levenshtein.c, similar to what's
> been done in help.c:help_unknown_cmd. However, where do you draw the
> lin
x27; would encounter and could help
the user with.
Yes. I like your suggestion of using levenshtein.c, similar to what's
been done in help.c:help_unknown_cmd. However, where do you draw the
line? Do you also suggest 'remotes/origin/foo' for 'remotes/foo'? Also,
wh
Vikrant Varma writes:
> On 02-05-2013 02:02, Ramkumar Ramachandra wrote:
>>> ref_cb.similar_refs has already been defined. The compiler won't let me
>>> assign to it unless I cast first. However, I think compound literals are a
>>> C99/gcc feature. Is this better?
>>>
>>> struct similar_
On 02-05-2013 02:02, Ramkumar Ramachandra wrote:
ref_cb.similar_refs has already been defined. The compiler won't let me
assign to it unless I cast first. However, I think compound literals are a
C99/gcc feature. Is this better?
struct similar_ref_cb ref_cb = {ref, STRING_LIST_INIT_NODU
Vikrant Varma wrote:
> I agree with Matthieu, the people who don't want to see this advice never
> will, because they won't make that mistake. Maybe advice is the wrong word,
> corrections might be more appropriate.
Makes sense.
Perhaps it would make sense to hook into help.autocorrect. I would
Am 01.05.2013 21:55, schrieb Vikrant Varma:
> On 01-05-2013 17:53, Ramkumar Ramachandra wrote:
>> Vikrant Varma wrote:
>>> +void help_unknown_ref(const char* ref) {
>>> +int i;
>>> +struct similar_ref_cb ref_cb;
>>> +ref_cb.similar_refs = (struct string_list)STRING_LIST_INIT
701 - 800 of 1049 matches
Mail list logo
