Sup Yut Sum ch3co...@gmail.com writes:
Signed-off-by: Sup Yut Sum ch3co...@gmail.com
---
contrib/completion/git-completion.bash | 19 ++-
1 file changed, 18 insertions(+), 1 deletion(-)
Aren't you missing a commit message?
-Keshav
--
To unsubscribe from this list: send the
The following message is a courtesy copy of an article
that has been posted to gmane.comp.version-control.git as well.
Junio C Hamano gits...@pobox.com writes:
Thomas Ackermann th.ac...@arcor.de writes:
But for the simple use case where you only have a master
branch I consider it not really
Duy Nguyen pclo...@gmail.com writes:
On Thu, Nov 21, 2013 at 6:48 PM, Jeff King p...@peff.net wrote:
@@ -1514,14 +1469,6 @@ unsigned long unpack_object_header_buffer(const
unsigned char *buf,
int unpack_sha1_header(git_zstream *stream, unsigned char *map, unsigned
long mapsize, void
Thomas Koch tho...@koch.ro writes:
But also from experience I can tell that without exception everybody whom I
teached Git understood it only after being introduced to the basic concepts
of
Git and how to inspect and operate them on the commandline. Others told me
from similar
Thomas Manson dev.mansontho...@gmail.com writes:
The problem is that in Bazaar, I've commited some big files (63MB
173MB), but this files are no longer in my project, only in the
revisions files of Bazaar and now Git.
I don't need this files to be pushed on Github.
How can I search
Finnerty, James M Mr CTR USA USASOC-SOAR
jim.finnerty@soar.army.mil writes:
Hi. I'm going to attempt to import a git database into Razor which is
linux rcs based. Does the linux version of git use rcs ?
If you're talking about the GNU rcs program, no, it does not.
-Keshav
--
To
are only
reading the list via actual email (as I am not such a person).
Keshav Kini keshav.k...@gmail.com writes:
What about just putting an extra blank line after every root commit line
(possibly except the last one)? That should make it plenty easy to see
where the root commits are in --oneline
Junio C Hamano gits...@pobox.com writes:
Roberto Tyley roberto.ty...@gmail.com writes:
On 21/09/2013 23:16, Keshav Kini wrote:
[SNIP]
This situation came about because the BFG Repo-Cleaner doesn't write new
reflog entries after creating its new objects and moving refs around.
True enough
Milton Soares Filho milton.soares.fi...@gmail.com writes:
On 25 October 2013 15:13, Junio C Hamano gits...@pobox.com wrote:
Milton Soares Filho milton.soares.fi...@gmail.com writes:
git log --graph --oneline
* a1
* a2
x a3
* b1
* b2
x b3
I agree that the
Stefan Beller stefanbel...@googlemail.com writes:
While I can understand 4 or 7 white spaces are fancy, we'd rather want
to use tabs throughout the whole document.
You missed lines 278 and 833. There are also some spaces around line
488, but maybe those are layout-relevant and so shouldn't be
Junio C Hamano gits...@pobox.com writes:
Roberto Tyley roberto.ty...@gmail.com writes:
On 21/09/2013 23:16, Keshav Kini wrote:
[SNIP]
This situation came about because the BFG Repo-Cleaner doesn't write new
reflog entries after creating its new objects and moving refs around.
True enough
Junio C Hamano gits...@pobox.com writes:
Yoshioka Tsuneo yoshiokatsu...@gmail.com writes:
git diff -M --stat can detect rename and show renamed file name like
foofoofoo = barbarbar. But if destination filename is long, the line
is shortened like ...barbarbar so there is no way to know whether
Sam Vilain s...@vilain.net writes:
On 10/11/2013 06:07 AM, Yoshioka Tsuneo wrote:
+prefix_len = ((prefix_len = 0) ? prefix_len :
0);
+strncpy(pre_arrow, arrow - prefix_len,
prefix_len);
+
I'm not sure if this was the best way to split my changes into commits.
Please let me know if it wasn't.
Keshav Kini (4):
git-svn.txt: fix AsciiDoc formatting error
git-svn.txt: reword description of gc command
git-svn.txt: replace .git with $GIT_DIR
git-svn.txt: elaborate on rev_map
definitions apparently can't start with
a '.' character.
Signed-off-by: Keshav Kini keshav.k...@gmail.com
---
Documentation/git-svn.txt | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/Documentation/git-svn.txt b/Documentation/git-svn.txt
index 62ec727..3ddf545 100644
As asterisks are used to indicate bold text in AsciiDoc, shell glob
expressions must be escaped appropriately.
Signed-off-by: Keshav Kini keshav.k...@gmail.com
---
Documentation/git-svn.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/git-svn.txt b
It's redundant to say that $GIT_DIR/svn/refname/unhandled.log or
$GIT_DIR/svn/refname/index is in .git/svn when $GIT_DIR is '.git', and
is wrong when $GIT_DIR is not '.git'
Also, a '/' was missing from the pathname $GIT_DIR/svn/refname/index .
Signed-off-by: Keshav Kini keshav.k...@gmail.com
a FILES section to the man page with a description of
what $GIT_DIR/svn/**/.rev_map* files are and how they are (re)built, and
links to this description from various other parts of the man page.
Signed-off-by: Keshav Kini keshav.k...@gmail.com
---
Documentation/git-svn.txt | 28
Jakub Narebski jna...@gmail.com writes:
Matthieu Moy Matthieu.Moy at imag.fr writes:
* git status now omits the prefix to make its output a comment in a
commit log editor, which is not necessary for human consumption.
+ Scripts that parse the output of git status are advised to use
+
Stefan Beller stefanbel...@googlemail.com writes:
According to
http://thread.gmane.org/gmane.comp.version-control.git/212649
Eric, the original author of ciabot, doesn't want the ciabot
no longer be included in git.git, hence the removal of the
whole directory.
I take it you mean that he
Jonathan Nieder jrnie...@gmail.com writes:
Taking a step back, the reader might wonder *why* he would want
to run git svn fetch to rebuilt these .rev_map.* files, and what
they are for.
Perhaps there should be a separate REVISION MAP section describing
this in more detail. Something as
Jonathan Nieder jrnie...@gmail.com writes:
Keshav Kini wrote:
I changed the wording of your first paragraph a bit according to what I
thought it meant. Does it still convey what you wanted to convey, and is
it still correct?
Mapping between Subversion revision numbers and Git commit
Jonathan Nieder jrnie...@gmail.com writes:
@@ -684,7 +687,7 @@ svn-remote.name.noMetadata::
+
This option can only be used for one-shot imports as 'git svn'
will not be able to fetch again without metadata. Additionally,
-if you lose your .git/svn/**/.rev_map.* files, 'git svn' will not
David Aguilar dav...@gmail.com writes:
On Tue, Sep 24, 2013 at 2:07 PM, Jona Christopher Sahnwaldt
j...@sahnwaldt.de wrote:
Hi,
maybe this has already been reported, but I didn't find it in the mail
archive.
If I understand correctly, after I clone a repo, I should be able to
switch to
of the 'fetch' command
to rectify this oversight, and also fixes an AsciiDoc escaping typo.
Signed-off-by: Keshav Kini keshav.k...@gmail.com
---
Documentation/git-svn.txt | 11 +++
1 file changed, 7 insertions(+), 4 deletions(-)
diff --git a/Documentation/git-svn.txt b/Documentation/git
Hello,
When trying out Roberto Tyley's BFG Repo-Cleaner program [1], I managed
to put a git repository in the following state:
[2] fs@erdos /tmp/bfg-test-repo $ cat .git/logs/HEAD
00afb9f9a0c87dba4a203413358984e9f4fa5ffb Keshav Kini keshav.k
Keshav Kini keshav.k...@gmail.com writes:
For example, if `git
reflog show HEAD` displayed this:
0123456 [stuff] foo
789abcd [stuff] bar
ef01234 [stuff] baz
Then I would expect the reflog data file for HEAD to look something like
this, where '.' represents an unknown hex digit
27 matches
Mail list logo
