"Documenation"?
rday
--
========
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.
Current "man git-add" emphasizes single letter interactive
shortcut commands with "[]".
Signed-off-by: Robert P. J. Day
---
diff --git a/Documentation/git-add.txt b/Documentation/git-add.txt
index 45652fe4a6..ad9bd7c7a6 100644
--- a/Documentation/git-add.txt
+++ b/Docum
e valid in that third case (at least for
"--mixed"). thoughts? is that just an oversight in the man page?
rday
--
================
Robert P. J. Day Ottawa, Ontario, CANADA
On Sun, 2 Dec 2018, Duy Nguyen wrote:
> On Sun, Dec 2, 2018 at 6:05 PM Robert P. J. Day wrote:
> > > Patch update>> 2
> > > staged unstaged path
> > > * 1:unchanged+1/-0 README.md
> > > * 2:unchanged+
On Sat, 8 Dec 2018, Duy Nguyen wrote:
> On Sat, Dec 8, 2018 at 5:08 PM Robert P. J. Day wrote:
> >
> >
> > from "man git-reset":
> >
> > SYNOPSIS
> > git reset [-q] [] [--] ...
> > git reset (--patch | -p) [] [--] [...]
> >
On Sat, 8 Dec 2018, Duy Nguyen wrote:
> On Sat, Dec 8, 2018 at 6:32 PM Robert P. J. Day wrote:
> >
> > On Sat, 8 Dec 2018, Duy Nguyen wrote:
> >
> > > On Sat, Dec 8, 2018 at 5:08 PM Robert P. J. Day
> > > wrote:
> > > >
> > >
On Sat, 8 Dec 2018, Duy Nguyen wrote:
> On Sat, Dec 8, 2018 at 6:32 PM Robert P. J. Day wrote:
> >
> > On Sat, 8 Dec 2018, Duy Nguyen wrote:
> >
> > > On Sat, Dec 8, 2018 at 5:08 PM Robert P. J. Day
> > > wrote:
> > > >
> > >
others are to keep up with changes to git. that said, i
definitely have ideas for more wide-ranging changes if i ever get the
time; i think some section re-ordering could be helpful but that's all
in due time.
i do what i can.
rday
--
t
$ git diff --
rday
--
================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca/dokuwiki
Twitter: http://
as part of an upcoming git class i'm delivering, i thought it would
be amusing to demonstrate the maximum length of colliding SHA-1
prefixes in a repository (in my case, i use the linux kernel git repo
for most of my examples).
is there a way to display the objects in the object database tha
On Sun, 2 Dec 2018, Ævar Arnfjörð Bjarmason wrote:
> On Sun, Dec 02 2018, Robert P. J. Day wrote:
>
> > as part of an upcoming git class i'm delivering, i thought it
> > would be amusing to demonstrate the maximum length of colliding
> > SHA-1 prefixes in a repo
patch mode -- certainly "p" doesn't do it. am i stupidly missing
something trivial? is the explanation misleading or inncomplete?
rday
--
Robert P. J. Day
On Sun, 2 Dec 2018, Kevin Daudt wrote:
> On Sun, Dec 02, 2018 at 11:30:19AM -0500, Robert P. J. Day wrote:
> >
> > testing adding by patch for the very first time (i've just never
> > needed this), and reading the "progit" book and reading the man page,
&
On Sun, 2 Dec 2018, SZEDER Gábor wrote:
> On Sun, Dec 02, 2018 at 11:30:19AM -0500, Robert P. J. Day wrote:
> >
> > testing adding by patch for the very first time (i've just never
> > needed this), and reading the "progit" book and reading the man page,
&
On Sun, 2 Dec 2018, SZEDER Gábor wrote:
> On Sun, Dec 02, 2018 at 11:30:19AM -0500, Robert P. J. Day wrote:
> >
> > testing adding by patch for the very first time (i've just never
> > needed this), and reading the "progit" book and reading the man page,
&
On Sun, 2 Dec 2018, Duy Nguyen wrote:
> On Sun, Dec 2, 2018 at 6:05 PM Robert P. J. Day wrote:
> > > Patch update>> 2
> > > staged unstaged path
> > > * 1:unchanged+1/-0 README.md
> > > * 2:unchanged+
would display exclusively
objects in the object store corresponding to objects that are suddenly
unreferenced due to the removal of a remote? i was just curious as it
would be neat to demo that in a class.
rday
--
Robert
so what is the difference?
rday
--
============
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca/dokuwiki
Twitter: http://twitter.com/
On Fri, 1 Jun 2018, Jeff King wrote:
> On Fri, Jun 01, 2018 at 04:14:12PM -0400, Robert P. J. Day wrote:
>
> > $ git config --global a.b.c.d.e rday
> >
> > huh ... seemed to work fine, and added this to my ~/.gitconfig:
> >
> > [a "b.c.d"]
> &g
s
the commit that was the basis of that stash to create the new branch.
so, does any stash operation actually need the originating branch
name? (i'm guessing no, but i've been wrong before.)
rday
--
==============
On Fri, 1 Jun 2018, Jeff King wrote:
> On Fri, Jun 01, 2018 at 04:14:12PM -0400, Robert P. J. Day wrote:
... snip ...
> > ok, so how on earth would i use "git config" at the command line
> > to set a config variable with some arbitrary level of subsections?
> >
Even though "--get-regex" appears to work with "git config", the
standard is to spell out the action in full.
Signed-off-by: Robert P. J. Day
---
this is the only occurrence i saw of this in the entire code base, so
it seemed worth tweaking just for consistency.
diff --
Even though "--get-regex" appears to work with "git config", the
clear standard is to spell out the action in full.
Signed-off-by: Robert P. J. Day
---
this is the only occurrence i saw of this in the entire code base, so
it seemed worth tweaking just for consistency.
On Sun, 3 Jun 2018, SZEDER Gábor wrote:
>
>
> > On Fri, 1 Jun 2018, Jeff King wrote:
> >
> > > On Fri, Jun 01, 2018 at 04:14:12PM -0400, Robert P. J. Day wrote:
> > > > ok, so how on earth would i use "git config" at the command line
> > &g
Fix single misspelling of $GITDIR to correct $GIT_DIR.
Signed-off-by: Robert P. J. Day
---
only occurrence in entire code base that i ran across, so i figured
might as well fix it.
diff --git a/sha1-file.c b/sha1-file.c
index 555e780f4..695e5c627 100644
--- a/sha1-file.c
+++ b/sha1-file.c
uing, so no need to resend.
argh, i actually know that, i just screwed up.
> On 06/03, Robert P. J. Day wrote:
> >
> > Even though "--get-regex" appears to work with "git config", the
> > clear standard is to spell out the action in full.
>
> --ge
Fix single misspelling of $GITDIR to correct $GIT_DIR in a comment.
Signed-off-by: Robert P. J. Day
---
updated patch to clarify that the misspelling is only in a comment.
diff --git a/sha1-file.c b/sha1-file.c
index 555e780f4..695e5c627 100644
--- a/sha1-file.c
+++ b/sha1-file.c
@@ -610,7
On Mon, 4 Jun 2018, Junio C Hamano wrote:
> "Robert P. J. Day" writes:
>
> > i realize that, when you "git stash push", stash graciously
> > saves the branch you were on as part of the commit message, but
> > does any subsequent stash operation tec
On Sun, 3 Jun 2018, Philip Oakley wrote:
> From: "Robert P. J. Day"
> > On Sun, 3 Jun 2018, Thomas Gummerer wrote:
> >> --get-regex works as the parse-option API allows abbreviations of
> >> the full option to be specified as long as the abbreviation is
>
Change deprecated "--set-upstream" branch option to
preferred "--set-upstream-to".
Signed-off-by: Robert P. J. Day
---
i'm assuming this should use "--set-upstream-to" as do all the
others.
diff --git a/t/t3200-branch.sh b/t/t3200-branch.sh
index 69
On Tue, 5 Jun 2018, SZEDER Gábor wrote:
> > Change deprecated "--set-upstream" branch option to
> > preferred "--set-upstream-to".
> >
> > Signed-off-by: Robert P. J. Day
> >
> > ---
> >
> > i'm assuming this should us
On Wed, 6 Jun 2018, Thomas Fischer wrote:
> OVERVIEW
>
> "git rm" will remove more files than specified. This is either a bug or
> undocumented behavior (not in the man pages).
>
> SETUP
>
> 1. In a git repository, create an empty directory OR a chain of empty
> directories
>
> $ mkdir -p path/t
n I run 'git rm path/to/some/file', I expect
> path/to/some/ to exist, *albeit untracked*.
again, why?
> I do NOT expect git to *track* empty directories. But I also do NOT
> expect it to remove untracked directories.
why not?
rday
--
======
making it clear what
happens in this case. i see no value in supporting extra options that
simply encourage bad behaviour.
rday
--
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.c
Use the obvious consensus of hyphenated "remote-tracking branch", and
fix an obvious typo, all in documentation and comments.
Signed-off-by: Robert P. J. Day
---
diff --git a/Documentation/git-submodule.txt b/Documentation/git-submodule.txt
index 4a5cc38a6f..ef9d9d28a9 10
ol,safecrlf,autocrlf}
- i'm sure there are client-side hooks that can be mentioned
etc, etc.
has anyone ever written a doc that collects these things in one
place? if not, i guess i have to write one.
rday
--
============
Signed-off-by: Robert P. J. Day
diff --git a/Documentation/diff-options.txt b/Documentation/diff-options.txt
index f466600972..30aad8396d 100644
--- a/Documentation/diff-options.txt
+++ b/Documentation/diff-options.txt
@@ -64,7 +64,7 @@ ifndef::git-format-patch[]
endif::git-format-patch
On Mon, 11 Jun 2018, Stefan Beller wrote:
> On Fri, Jun 8, 2018 at 10:15 AM Derrick Stolee wrote:
> >
> > On 6/8/2018 9:18 AM, Robert P. J. Day wrote:
> > >for one of my courses, i wanted to write a section about the
> > > various techniques for dealing
git admins can testify really make sense to set in a corporate
environment. does that make sense?
open to thoughts ...
rday
--
============
Robert P. J. Day Ottawa, Ontario, CANADA
http:/
the use of what
are clearly the default files. thoughts?
rday
--
============
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca/dokuwiki
Twitter:
On Tue, 26 Jun 2018, Jeff King wrote:
> On Tue, Jun 26, 2018 at 06:18:26AM -0400, Robert P. J. Day wrote:
>
> >
> > ENVIRONMENT
> > GIT_CONFIG
> > Take the configuration from the given file instead of
> > .git/config. Using
was just perusing the sample hook scripts, and the sample pre-commit
script provided with git does the following check:
# If you want to allow non-ASCII filenames set this variable to true.
allownonascii=$(git config --bool hooks.allownonascii)
but that config variable (hooks.allownonascii)
On Tue, 19 Feb 2019, Ævar Arnfjörð Bjarmason wrote:
>
> On Tue, Feb 19 2019, Robert P. J. Day wrote:
>
> > was just perusing the sample hook scripts, and the sample pre-commit
> > script provided with git does the following check:
> >
> > # If you want to a
The default pre-commit script checks the config variable
"hooks.allownonascii" to determine whether to allow non-ASCII file
names -- mention this in "man githooks", just as the section on
"update" mentions the use of "hooks.allowunannotated".
Signed-off-
esses
those two arguments, as "v4.19" is, of course, a reference to a
specific commit, but "^v4.19^" appears to define all those commits not
reachable from "v4.19^". how should one read this?
rday
--
=
works fine.
the question is, is it not inconsistent for fedora's basic "git"
package to include the man page for gitweb, without including the
corresponding functionality? is this something i should submit a
fedora bugzilla report for? or am i misunderstanding somethi
perusing the source code
doesn't seem to show that command checking that config option.
am i misreading something? and if not, is there a reason git clean
does not consult core.excludesFile?
rday
--
============
On Sat, 23 Feb 2019, Todd Zullinger wrote:
> Hi,
>
> Robert P. J. Day wrote:
> >
> > not so much a git issue as what looks like a fedora packaging
> > issue.
>
> Yeah, it's just a minor packaging issue. The gitweb manpages are
> included in the m
On Sat, 23 Feb 2019, Johannes Schindelin wrote:
> Hi,
>
> On Sat, 23 Feb 2019, Johannes Schindelin wrote:
>
> > On Sat, 23 Feb 2019, Junio C Hamano wrote:
> >
> > > "Robert P. J. Day" writes:
> > >
> > > > am i misreading som
argv_array_push(&repack, "-a");
else {
... snip ...
while the man page does not seem to mention the possible value of
"now".
am i misreading something? should the man page mention the possible
value of "now" as opposed to "all"?
rday
--
Signed-off-by: Robert P. J. Day
---
diff --git a/Documentation/git-gc.txt b/Documentation/git-gc.txt
index a7442499f6..a7c1b0f60e 100644
--- a/Documentation/git-gc.txt
+++ b/Documentation/git-gc.txt
@@ -76,7 +76,7 @@ be performed as well.
--prune=::
Prune loose objects older than
any further. (yes, i
realize that, if you read carefully, it *should* make it clear, but i
think it would be helpful to at least graphically show that
happening.)
thoughts?
rday
--
================
Robert P. J. Day
before running the rebase, then leaving off that final argument?
everything i've seen suggests those two things are identical, but
i've been fooled before.
rday
--
============
Robert P. J. Day
arify that.
Signed-off-by: Robert P. J. Day
---
diff --git a/Documentation/git-rebase.txt b/Documentation/git-rebase.txt
index 5629ba4c5d..ba3c44fdaf 100644
--- a/Documentation/git-rebase.txt
+++ b/Documentation/git-rebase.txt
@@ -109,8 +109,8 @@ functionality which is found in 'next'.
On Tue, 5 Mar 2019, Junio C Hamano wrote:
> "Robert P. J. Day" writes:
>
> > one of the things i've noticed about the examples in "man
> > git-rebase" is that they invariably show rebasing relative to a
> > branch point that has not moved. fo
On Tue, 5 Mar 2019, Junio C Hamano wrote:
> "Robert P. J. Day" writes:
>
> > Currently, all of the examples for "man git-rebase" show rebasing from
> > a branch that has had no further development, which might mislead
> > readers into thinking tha
Correct misspelled ".gitattribute" in comments only, so no functional
change.
Signed-off-by: Robert P. J. Day
---
diff --git a/attr.c b/attr.c
index fdd110bec5..93dc16b59c 100644
--- a/attr.c
+++ b/attr.c
@@ -431,14 +431,14 @@ static struct match_attr *parse_attr_line(const c
nio's
take on this here:
https://marc.info/?l=git&m=152695527902711&w=2
was to banish the phrase entirely in favour of some combination of
"tracked" and/or "added to the index."
thoughts?
rday
--
================
utting in an
extra line or two mentioning this in the man page? that is, as long as
i've understood this correctly.
rday
--
================
Robert P. J. Day Ottawa, Ontario, CANADA
http
age
collected?
rday
--
================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca/dokuwiki
Twitter: http://twitter.com/rpjday
LinkedIn:
t;all") || !strcmp(date, "now"))
... snip ...
is the preference to simply list both alternatives, or to
*encourage* the more intuitive "now" and "never" values while politely
deprecating the others? the impression i get is the latter.
rday
-
quot; that the
revert was cancelled:
Aborting commit due to empty commit message.
that seems ... inconsistent. am i misunderstanding something?
rday
--
Robert P. J. Day Ottawa, Onta
On Tue, 12 Mar 2019, Bryan Turner wrote:
> On Tue, Mar 12, 2019 at 10:23 AM Robert P. J. Day
> wrote:
> >
> > never noticed this before ... when i do a regular "git commit" and
> > enter my "vi" edit session and change my mind, i can bail with &q
On Tue, 12 Mar 2019, Bryan Turner wrote:
> On Tue, Mar 12, 2019 at 10:23 AM Robert P. J. Day
> wrote:
> >
> > never noticed this before ... when i do a regular "git commit" and
> > enter my "vi" edit session and change my mind, i can bail with &q
ah, i'm starting to get it. predictably, i think this needs to be
mentioned in a man page. :-) thanks muchly for clearing that up.
rday
--
================
Robert P. J. Day Ottawa, Ontario, CANADA
On Tue, 12 Mar 2019, Bryan Turner wrote:
> On Tue, Mar 12, 2019 at 11:01 AM Robert P. J. Day
> wrote:
> >
> > On Tue, 12 Mar 2019, Bryan Turner wrote:
> >
> > > On Tue, Mar 12, 2019 at 10:23 AM Robert P. J. Day
> > > wrote:
> > > >
>
On Thu, 14 Mar 2019, Konstantin Ryabitsev wrote:
> On Wed, 13 Mar 2019 at 16:56, Jeff King wrote:
> > - preferences between Canada and US?
>
> If you're looking at Canada, East coast is generally more affordable
> than West Coast in terms of venues and accommodation. The three main
> tech hubs
clearly don't understand
what this option is supposed to do.
rday
--
================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca/dokuwiki
Twitter:
On Fri, 15 Mar 2019, Duy Nguyen wrote:
> On Fri, Mar 15, 2019 at 7:17 PM Robert P. J. Day
> wrote:
> >
> >
> > probably doing something idiotic but i'm enumerating variations of
> > shallow cloning, and tried the following:
> >
> > $ git cl
On Fri, 15 Mar 2019, Duy Nguyen wrote:
> On Fri, Mar 15, 2019 at 8:19 PM Robert P. J. Day
> wrote:
> > this is the first time i've played with this feature, so i'm
> > still working my way through the man page, trying to figure out
> > the various vali
On Sat, 16 Mar 2019, Duy Nguyen wrote:
> On Fri, Mar 15, 2019 at 9:31 PM Robert P. J. Day
> wrote:
> > also, i think "man git-clone" could really use a set of examples for
> > shallow cloning. i'd offer to write it but i'm still figuring it out.
>
>
l,space
does the "!" apply to "indent" or to the entire list? the man page
doesn't say.
just being pedantic again.
rday
--
================
Robert P. J. Day Ottawa, Ontario, CANADA
On Sat, 16 Mar 2019, Ævar Arnfjörð Bjarmason wrote:
>
> On Sat, Mar 16 2019, Robert P. J. Day wrote:
>
> > more nitpicking, but i'm working my way through the intricacies of
> > attributes and putting together some (allegedly) simple examples for a
> > class i&#
On Sat, 16 Mar 2019, Johannes Sixt wrote:
> Am 16.03.19 um 13:22 schrieb Robert P. J. Day:
> > as a working example, i looked at the top-level .gitattributes file
> > in the git source code itself, which opens with:
> >
> > * whitespace=!indent,trail,space
> >
. i have no idea
what relationship those packages have to official git, or who decides
what goes into them.
rday
--
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca/dokuwiki
Twitter:
(technically not a git question, but i kind of need to know the
answer to this quickly as i'm writing some documentation and this is
something i have to explain.)
i cloned a repository (hyperledger fabric) which has a top-level
.gitreview file:
[gerrit]
host=gerrit.hyperledger.org
port
On Sat, 31 Mar 2018, Ævar Arnfjörð Bjarmason wrote:
> On Sat, Mar 31, 2018 at 9:04 PM, Robert P. J. Day
> wrote:
> >
> > (technically not a git question, but i kind of need to know the
> > answer to this quickly as i'm writing some documentation and this is
&g
never had cause to examine "git remote set-url" before so i'm a bit
puzzled by this part of the man page:
set-url
Changes URLs for the remote. Sets first URL for remote
that matches regex ...
With --push, push URLs are manipulated instead of fetch URLs.
.. snip ...
Note that the
another feature i've seen for the very first time ... working with
kubernetes so i checked it out of github, and part of the instructions
for that is to make sure you don't accidentally try to push back to
the github remote, so the directions suggest:
$ git remote add upstream https://github.com
On Mon, 16 Apr 2018, Andreas Schwab wrote:
> On Apr 16 2018, "Robert P. J. Day" wrote:
>
> > i don't understand how you can clearly set the fetch and push URLs
> > of a remote independently, while the man page nonetheless insists
> > that "even th
On Tue, 17 Apr 2018, Junio C Hamano wrote:
> Jacob Keller writes:
>
> > Things won't work so well if you set the push url and fetch url to
> > different repositories. Git assumes that refs updated by "push"
> > will also be reflected via "fetch".
> >
> > I don't know offhand what will break, but
While the "git reflog" man page supports both "--dry-run" and "-n" for
a dry run, the man page mentions only the former, not the latter.
Signed-off-by: Robert P. J. Day
---
--- a/Documentation/git-reflog.txt
+++ b/Documentation/git-reflog.txt
@@ -20,9 +20,9
ndering why some commands feel the need to
explain the function of "--", when that's the sort of thing that more
properly belongs in "man gitcli".
thoughts?
rday
--
Robert P. J. Day Ottawa, Ontario,
While the "git reflog" man page supports both "--dry-run" and "-n" for
a dry run, the man page mentions only the former, not the latter.
Signed-off-by: Robert P. J. Day
---
sorry, i accidentally chopped off the leading lines of the patch in
the earlier post.
Add mention of git prune's "--progress" option to the SYNOPSIS and
DESCRIPTION sections of the man page, and to the usage message of "git
prune" itself.
While we're here, move the explanation of "--" toward the end of the
DESCRIPTION section, where it b
page.
Signed-off-by: Robert P. J. Day
---
diff --git a/Documentation/git-notes.txt b/Documentation/git-notes.txt
index 43677297f..c75748963 100644
--- a/Documentation/git-notes.txt
+++ b/Documentation/git-notes.txt
@@ -18,7 +18,7 @@ SYNOPSIS
'git notes' merge --commit [-v | -q]
On Tue, 21 Nov 2017, Jonathan Nieder wrote:
> Hi,
>
> Robert P. J. Day wrote:
>
> > It seems clear that the man page SYNPOSIS and the usage message
> > referring to:
> >
> > git notes prune [-n | -v]
> >
> > is incorrect, as "-n" (dr
Currently, 'git notes prune' in man page and usage message
incorrectly lists options as '[-n | -v]', rather than '[-n] [-v]'.
Signed-off-by: Robert P. J. Day
---
i think i got it right this time.
diff --git a/Documentation/git-notes.txt b/Documentation
No major changes, just some rewording and showing some variations of
general Git commands.
Signed-off-by: Robert P. J. Day
---
diff --git a/Documentation/gitcli.txt b/Documentation/gitcli.txt
index 9f13266a6..a4efcb7ce 100644
--- a/Documentation/gitcli.txt
+++ b/Documentation/gitcli.txt
"man gitcli" already explains the purpose of the "--" syntax, so there
is no value to a small subset of Git commands explaining that in their
man pages.
Signed-off-by: Robert P. J. Day
---
i tried this once before, and i'm going to try to push it through
aga
On Tue, 21 Nov 2017, Jonathan Nieder wrote:
> Hi,
>
> Robert P. J. Day wrote:
>
> > following up on an earlier question of mine, is there a standard
> > for what options should be listed in either the SYNOPSIS or the
> > DESCRIPTION sections of a man page? i ask sinc
On Tue, 21 Nov 2017, Eric Sunshine wrote:
> On Tue, Nov 21, 2017 at 3:53 PM, Robert P. J. Day
> wrote:
> > No major changes, just some rewording and showing some variations of
> > general Git commands.
> >
> > Signed-off-by: Robert P. J. Day
> > ---
> &g
No major changes, just some rewording and showing some variations of
general Git commands.
Signed-off-by: Robert P. J. Day
---
diff --git a/Documentation/gitcli.txt b/Documentation/gitcli.txt
index 9f13266a6..d690d1ff0 100644
--- a/Documentation/gitcli.txt
+++ b/Documentation/gitcli.txt
On Tue, 21 Nov 2017, Kevin Daudt wrote:
> On Tue, Nov 21, 2017 at 04:27:59PM -0500, Robert P. J. Day wrote:
> > No major changes, just some rewording and showing some variations of
> > general Git commands.
> >
> > Signed-off-by: Robert P. J. Day
> >
> >
On Tue, 21 Nov 2017, Kevin Daudt wrote:
> On Tue, Nov 21, 2017 at 04:47:42PM -0500, Robert P. J. Day wrote:
> > On Tue, 21 Nov 2017, Kevin Daudt wrote:
> >
> > > On Tue, Nov 21, 2017 at 04:27:59PM -0500, Robert P. J. Day wrote:
> > > > No major changes,
On Wed, 22 Nov 2017, Junio C Hamano wrote:
> "Robert P. J. Day" writes:
>
> > While the "git reflog" man page supports both "--dry-run" and "-n" for
> > a dry run, the man page mentions only the former, not the latter.
> >
> &g
On Tue, 21 Nov 2017, Kevin Daudt wrote:
> On Tue, Nov 21, 2017 at 04:27:59PM -0500, Robert P. J. Day wrote:
> > No major changes, just some rewording and showing some variations of
> > general Git commands.
> >
> > Signed-off-by: Robert P. J. Day
> >
> >
On Wed, 22 Nov 2017, Junio C Hamano wrote:
> "Robert P. J. Day" writes:
>
> > i appreciate the need for brevity, but this just takes us back
> > to, is there a standard for man pages, given how they bounce
> > around all over the place?
> >
> >
On Wed, 22 Nov 2017, Junio C Hamano wrote:
> "Robert P. J. Day" writes:
>
> > git repo with a file called "Gemfile", so i created a branch called
> > "Gemfile", and when i ran:
> >
> > $ git checkout Gemfile
> >
> > git s
On Wed, 22 Nov 2017, Kevin Daudt wrote:
> On Wed, Nov 22, 2017 at 06:19:23AM -0500, Robert P. J. Day wrote:
> > On Wed, 22 Nov 2017, Junio C Hamano wrote:
> >
> > > "Robert P. J. Day" writes:
> > >
> > > > git repo with a file called "G
1 - 100 of 257 matches
Mail list logo
