On Tue, Nov 19, 2013 at 11:43 PM, Junio C Hamano gits...@pobox.com wrote:
Jason St. John jstj...@purdue.edu writes:
Documentation/git-rebase.txt: add a blank line after the two AsciiDoc
listing blocks
That looks funnily formatted, out of place and redundant.
Without these blank lines
On Mon, Jan 13, 2014 at 12:55 PM, Junio C Hamano gits...@pobox.com wrote:
Jason St. John jstj...@purdue.edu writes:
What AsciiDoc formatter (and version) do you use?
$ asciidoc --version
asciidoc 8.6.8
Checking with www.methods.co.nz/asciidoc, I am behind by about 2
months
On Wed, Mar 19, 2014 at 8:09 PM, 乙酸鋰 ch3co...@gmail.com wrote:
Hi,
Where to find git 1.9.1 tarball?
It is not uploaded to google code.
--
You can download a tarball for 1.9.1 from GitHub:
https://github.com/git/git/archive/v1.9.1.tar.gz
Jason
--
To unsubscribe from this list: send the line
On Thu, Mar 20, 2014 at 6:16 PM, Justin Lebar jle...@google.com wrote:
Signed-off-by: Justin Lebar jle...@gmail.com
---
Makefile| 2 +-
builtin/apply.c | 2 +-
builtin/checkout.c | 2 +-
builtin/log.c
On Thu, Mar 20, 2014 at 7:13 PM, Justin Lebar jle...@google.com wrote:
Thanks for the quick reply.
When I send a new patch, should I fold these changes into the original
commit, or should I send them as a separate commit?
diff --git a/builtin/apply.c b/builtin/apply.c
index b0d0986..6013e19
On Sat, Mar 29, 2014 at 6:59 PM, Justin Lebar jle...@google.com wrote:
This version applies successfully to master, maint, next, and pu. The other
patches in the previous version of this queue apply successfully without any
changes.
Signed-off-by: Justin Lebar jle...@google.com
---
On Mon, May 5, 2014 at 12:53 AM, Felipe Contreras
felipe.contre...@gmail.com wrote:
Scott Chacon wrote:
The GitHub training team has all of their materials open sourced under
a CC BY 3.0 license. They're all written in Markdown and hosted on
GitHub. You can check them out here, including
Signed-off-by: Jason St. John jstj...@purdue.edu
---
Junio pointed out in the link below that there are a number of instances of e.g.
command line option (without a hyphen) in the documentation. This patch fixes
all of them that I was able to find. The other minor grammatical improvements
were
On Wed, May 21, 2014 at 2:52 PM, Jason St. John jstj...@purdue.edu wrote:
Signed-off-by: Jason St. John jstj...@purdue.edu
---
Junio pointed out in the link below that there are a number of instances of
e.g.
command line option (without a hyphen) in the documentation. This patch
fixes
On Wed, Nov 12, 2014 at 2:17 PM, Joe DF jo...@live.ca wrote:
Hello, i have a patch here for the git docs.
There is a typo.
See: https://github.com/git/git/pull/103/files
cheers,
-
Joe DF--
To unsubscribe from this list: send the line unsubscribe git in
git-log.txt: grammatical fixes under --log-size option
Signed-off-by: Jason St. John jstj...@purdue.edu
---
Documentation/git-log.txt | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/Documentation/git-log.txt b/Documentation/git-log.txt
index 34097ef..243a9c5 100644
with
their ASCIIDOC equivalent (e.g. a - character becomes
a ``-'' character,
Signed-off-by: Jason St. John jstj...@purdue.edu
---
Sorry for the messy quoting in the last set of examples in the commit message.
There wasn't really any way to work around it other than omitting the quotes
around
timezone is two words, not one (i.e. time zone is correct).
Correct this in these files:
-- date-formats.txt
-- git-blame.txt
-- git-cvsimport.txt
-- git-fast-import.txt
-- git-svn.txt
-- gitweb.conf.txt
-- rev-list-options.txt
Signed-off-by: Jason St. John jstj...@purdue.edu
---
Sources:
(1
timezone is two words, not one (i.e. time zone is correct).
Signed-off-by: Jason St. John jstj...@purdue.edu
---
I broke this off into a separate patch in case the release notes are
essentially fixed in history and typos, misspellings, etc. don't get
corrected.
Sources are provided below
=oneline` instead of `\--pretty=oneline`).
Signed-off-by: Jason St. John jstj...@purdue.edu
---
This was discussed here:
http://marc.info/?l=gitm=138419319223845w=2
http://marc.info/?l=gitm=138424552300662w=2
Documentation/CodingGuidelines | 22 +++---
1 file changed, 19
reworded some sentences for easier reading
-- fix some typos (e.g. show - shown)
Signed-off-by: Jason St. John jstj...@purdue.edu
---
This is a resubmit of patch 2/4 from my earlier patchset:
http://marc.info/?l=gitm=138395814108214w=2
Documentation/rev-list-options.txt | 136
Documentation/git-log.txt:
--log-size was added in commit 9fa3465, and the commit message contained
a satisfactory explanation; however, the man page entry for it was
unclear and cryptic.
Thanks-to: Jonathan Nieder jrnie...@gmail.com
Signed-off-by: Jason St. John jstj...@purdue.edu
to section headings
-- use backticks around option arguments/defaults
Signed-off-by: Jason St. John jstj...@purdue.edu
---
When working on this commit, I noticed a difference in how options and
option descriptions are separated (e.g. with a blank line or not). At least
with Vim's syntax
St. John jstj...@purdue.edu
---
This is a resubmit of a previous patch:
http://marc.info/?l=gitm=138431653412495w=2
I added a Thanks-to for Stuart Rackham because he's listed as the author of the
AsciiDoc User Guide, which part of this commit relies heavily on.
Documentation/CodingGuidelines
'')
Signed-off-by: Jason St. John jstj...@purdue.edu
---
This is a resubmit of a previous patch:
http://marc.info/?l=gitm=138431995913311w=2
I decided to remove the blank lines after option subheadings because the syntax
highlighting in Vim actually looks better with them removed. I'm not sure how
St. John jstj...@purdue.edu
---
I changed E-mail to email because that is clearly the dominant form:
http://www.google.com/trends/explore?q=#q=%22email%22%2C%20%22E-mail%22cmpt=q
Documentation/rev-list-options.txt | 27 ++-
1 file changed, 14 insertions(+), 13 deletions
On Wed, Nov 13, 2013 at 4:56 PM, Junio C Hamano gits...@pobox.com wrote:
Jason St. John jstj...@purdue.edu writes:
Documentation/git-log.txt:
-- replace single quotes around options/commands with backticks
-- use single quotes around references to sections
-- replaced some double quotes
On Thu, Nov 14, 2013 at 8:44 PM, Jason St. John jstj...@purdue.edu wrote:
On Wed, Nov 13, 2013 at 4:56 PM, Junio C Hamano gits...@pobox.com wrote:
Jason St. John jstj...@purdue.edu writes:
Documentation/git-log.txt:
-- replace single quotes around options/commands with backticks
-- use
-off-by: Jason St. John jstj...@purdue.edu
---
You can see the carnage here:
http://git-scm.com/docs/git-rebase#_bugs
This fixes GitHub issue github/gitscm-next#281
https://github.com/github/gitscm-next/issues/281
Documentation/git-rebase.txt | 2 ++
1 file changed, 2 insertions(+)
diff --git
On Tue, Nov 19, 2013 at 7:31 PM, Jonathan Nieder jrnie...@gmail.com wrote:
Hi,
Jason St. John wrote:
Documentation/git-rebase.txt: add a blank line after the two AsciiDoc
listing blocks
I'd leave out the above two description lines, since they're redundant
next to the patch text.
I
Replace double quotes around literal examples with backticks
Signed-off-by: Jason St. John jstj...@purdue.edu
---
Documentation/gitcli.txt | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/Documentation/gitcli.txt b/Documentation/gitcli.txt
index 3146413..41bed29
On Tue, Nov 19, 2013 at 8:50 PM, Tim Chase g...@tim.thechases.com wrote:
Having lost add -p work enough times when stashing, I finally
dug into the docs to see how to prevent it, discovering that
--keep-index does exactly what I want. However, now I have trouble
remembering to add the
On Tue, Mar 10, 2015 at 1:23 PM, Junio C Hamano gits...@pobox.com wrote:
Christian Couder christian.cou...@gmail.com writes:
I don't want to write again about each of these points now. I am more
interested in discussing a good strategy to try to revert the sad
trend of Git developers being
28 matches
Mail list logo