Hi,
if I clone a remote head other than master via Cogito with
cg-clone host:path#remoteHead,
work on this branch, and try to push back my changes with
cg-push,
I get the error
pushing to a different head not supported yet.
As far as I can see, there is no support in
On Thursday 28 July 2005 17:56, Johannes Schindelin wrote:
localhead=remotehead. BTW, this whole multihead mess applies only to Jeffs
anyway :-)
GIT/Cogito usage is not about linux kernel only.
I actually try to work with a scenario for a project with a few developers,
where each one should
On Sunday 31 July 2005 22:15, Junio C Hamano wrote:
Josef Weidendorfer [EMAIL PROTECTED] writes:
+It is assured that sha1-old is an ancestor of sha1-new (otherwise,
+the update would have not been allowed). refname is relative to
+$GIT_DIR; e.g. for the master head this is refs/heads/master
On Wednesday 03 August 2005 18:50, you wrote:
Hi,
On Wed, 3 Aug 2005, Linus Torvalds wrote:
Are you sure you have a good git version on master? I've never seen
anything like that, and I push all the time..
Call him Zaphod: he has two heads (master and pu). You don't. As I said in
another
On Wednesday 03 August 2005 19:37, you wrote:
Linus Torvalds [EMAIL PROTECTED] writes:
I started out to make the -f flag to send-file work around it, but I
never finished that, partly because it really ends up being the same
thing as git-fetch-pack in reverse, which was against the whole
On Wednesday 03 August 2005 19:08, you wrote:
Yes it is. To reproduce:
You do not need 2 clones.
It is enough to have one clone with a branch, and you make a commit in the
original repository.
Afterwards, pushing a new commit from the clone gives the error.
After pulling the missing commit
On Wednesday 03 August 2005 20:07, Junio C Hamano wrote:
Josef, could you give it a try please?
Perfect. Thanks.
Josef
-
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Monday 08 August 2005 11:55, Johannes Schindelin wrote:
Hi,
On Mon, 8 Aug 2005, Josef Weidendorfer wrote:
IMHO, $GIT_DIR/branches/ is really confusing.
Hmmm... in $GIT_DIR/branches/ there are named references to remote
(named) references.
Not necessarily. The following is perfectly
On Sunday 31 July 2005 21:17, Josef Weidendorfer wrote:
Added hook in git-receive-pack
Regarding the update hook:
In this script, it would be nice to be able to distinguish rebasing/forced
setting of a head from a regular fast forwarding. In the first case, I do not
want to potentially send
On Saturday 13 August 2005 21:27, Junio C Hamano wrote:
Josef Weidendorfer [EMAIL PROTECTED] writes:
Or is there already an easy way to detect the fast-forward situation in
the script?
Since you are given old and new, presumably you can do
merge-base in the hook to see what it yields?
Ah
On Saturday 13 August 2005 11:08, Junio C Hamano wrote:
Also add --verify to make sure the lines you introduced are
clean, which is more useful in commit but not very much in
format-patch as it was originally implemented, because finding
botches at format-patch time is too late.
I think that
On Thursday 18 August 2005 09:24, Junio C Hamano wrote:
$ cat $GIT_DIR/remotes/www
URL: http://www.kernel.org/pub/scm/git/git.git/
Pull: master:ko-master pu:ko-pu
Push: master:master pu:pu foo:bar
Isn't this mixing two kinds of information:
1) Some default/persistent
12 matches
Mail list logo