From: "J. Bruce Fields" <bfields@fieldses.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: patches
Date: Mon, 26 Nov 2007 02:27:45 +0000 [thread overview]
Message-ID: <20071126022745.GI23820@fieldses.org> (raw)
There's some more user-manual stuff in the git repository at
ssh://linux-nfs.org/~bfields/exports/git.git maint
J. Bruce Fields (4):
user-manual: define "branch" and "working tree" at start
user-manual: failed push to public repository
user-manual: clarify language about "modifying" old commits
user-manual: recovering from corruption
Documentation/user-manual.txt | 225 ++++++++++++++++++++++++++++++++++++-----
1 files changed, 201 insertions(+), 24 deletions(-)
--b.
commit 1cdade2c4cb27f648a98d326ef3db523b6afafa7
Author: J. Bruce Fields <bfields@citi.umich.edu>
Date: Sat Mar 3 22:53:37 2007 -0500
user-manual: recovering from corruption
Some instructions on dealing with corruption of the object database.
Most of this text is from an example by Linus, identified by Nicolas
Pitre <nico@cam.org> with a little further editing by me.
Signed-off-by: "J. Bruce Fields" <bfields@citi.umich.edu>
commit 7cb192eab0251911e2ca77d4ecceb621dd2d34f5
Author: J. Bruce Fields <bfields@citi.umich.edu>
Date: Sun Nov 25 19:01:57 2007 -0500
user-manual: clarify language about "modifying" old commits
It's important to remember that git doesn't really allowing "editing" or
"modifying" commits, only replacing them by new commits. Redo some of
the language to make this clearer.
Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu>
commit 81eb417ad423ef7e8d088d517f89d3bda92f9c06
Author: J. Bruce Fields <bfields@citi.umich.edu>
Date: Sun Nov 25 17:54:19 2007 -0500
user-manual: failed push to public repository
More details on the case of a failed push to a public (non-shared)
repository.
Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu>
commit 0c4a33b54f3dbb9fa8cd2f5cf0e2a6363849d899
Author: J. Bruce Fields <bfields@citi.umich.edu>
Date: Sun Nov 25 13:53:37 2007 -0500
user-manual: define "branch" and "working tree" at start
Some explanation here might help.
Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu>
next reply other threads:[~2007-11-26 2:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-26 2:27 J. Bruce Fields [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-09-05 23:24 patches Patrick Mauritz
2005-09-08 2:06 ` patches Junio C Hamano
2005-09-08 10:11 ` patches Patrick Mauritz
2005-09-09 22:25 ` patches Jason Riedy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071126022745.GI23820@fieldses.org \
--to=bfields@fieldses.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).