From: Philip Oakley philipoak...@iee.org
Sent: Saturday, August 31, 2013 11:16 PM
From: Christian Couder chrisc...@tuxfamily.org
Signed-off-by: Christian Couder chrisc...@tuxfamily.org
---
Documentation/git-replace.txt | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git
Philip Oakley philipoak...@iee.org writes:
From: Philip Oakley philipoak...@iee.org
Sent: Saturday, August 31, 2013 11:16 PM
From: Christian Couder chrisc...@tuxfamily.org
Signed-off-by: Christian Couder chrisc...@tuxfamily.org
---
Documentation/git-replace.txt | 4 +++-
1 file changed, 3
On Mon, Sep 2, 2013 at 11:50 PM, Philip Oakley philipoak...@iee.org wrote:
From: Christian Couder chrisc...@tuxfamily.org
You mean something like the following:
$ cat ./graft2replace.sh
#!/bin/bash
while read orig parents
do
printf %s git cat-file commit $orig
printf %s
From: Christian Couder chrisc...@tuxfamily.org
From: Philip Oakley philipoak...@iee.org
From: Christian Couder chrisc...@tuxfamily.org
Maybe we can show that in an example. But I think the patch is quite
clear as it is and should be enough.
If we really want to correct some false beliefs,
Hi,
Philip Oakley wrote:
Does `hash-object` do the inverese of `cat-file commit`?
I didn't find the hash-object(1) man page very informative on that matter
Hm. The manpage says:
Computes the object ID value for an object with specified type
with the contents of the named
From: Jonathan Nieder jrnie...@gmail.com
Hi,
Philip Oakley wrote:
Does `hash-object` do the inverese of `cat-file commit`?
I didn't find the hash-object(1) man page very informative on that
matter
Hm. The manpage says:
Computes the object ID value for an object with specified type
with
Philip Oakley wrote:
The problem is the file format, in the sense that the earlier `git cat-file
commit $orig` has a human readable output which is a description of the
commit header, rather than the specific binary content.
Ah. That's the actual raw commit object format, though.
The
From: Jonathan Nieder jrnie...@gmail.com
Philip Oakley wrote:
The problem is the file format, in the sense that the earlier `git
cat-file
commit $orig` has a human readable output which is a description of
the
commit header, rather than the specific binary content.
Ah. That's the actual
From: Philip Oakley philipoak...@iee.org
From: Christian Couder chrisc...@tuxfamily.org
The replaced object and the replacement object must be of the same
type.
-There is no other restriction on them.
+This restriction can be bypassed using `-f`.
Unless `-f` is given, the 'replace'
From: Christian Couder chrisc...@tuxfamily.org
From: Philip Oakley philipoak...@iee.org
From: Christian Couder chrisc...@tuxfamily.org
The replaced object and the replacement object must be of the same
type.
-There is no other restriction on them.
+This restriction can be bypassed using
Signed-off-by: Christian Couder chrisc...@tuxfamily.org
---
Documentation/git-replace.txt | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/Documentation/git-replace.txt b/Documentation/git-replace.txt
index 736b48c..a2bd2ee 100644
--- a/Documentation/git-replace.txt
+++
From: Christian Couder chrisc...@tuxfamily.org
Signed-off-by: Christian Couder chrisc...@tuxfamily.org
---
Documentation/git-replace.txt | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/Documentation/git-replace.txt
b/Documentation/git-replace.txt
index 736b48c..a2bd2ee
12 matches
Mail list logo