From: Wolfgang Jenkner <wjenkner@inode.at>
To: emacs-devel@gnu.org
Cc: Felipe Contreras Garza <felipe.contreras@gmail.com>
Subject: Re: participation & contribution [was: Latest changes with lisp/uni-*.el and leim/quail]
Date: Tue, 03 Dec 2013 21:03:13 +0100 [thread overview]
Message-ID: <857gblofu0.fsf@iznogoud.viz> (raw)
In-Reply-To: 87eh5uqka9.fsf@zigzag.favinet
On Tue, Dec 03 2013, Thien-Thi Nguyen wrote:
> () Rüdiger Sonderfeld <ruediger@c-plusplus.de>
> () Mon, 02 Dec 2013 14:29:53 +0100
> Is anybody here using git-bzr to push to the Emacs master?
>
> Soon that would be me (and you, right?), and hopefully OP...
>
> How well does this work?
>
> Why don't you try it and post your observations? That's what i will do.
Like other people I have done some experiments with local repositories
and there is a thing that bothers me: While, by default, `git push' to
some other git repo succeeds only if this would not change the history
of what is already in that repo, there is apparently no such safeguard
against rewriting history in an upstream bzr repo (and pushing to
a bound branch instead does not quite work).
The stuff below corresponds to "NOTE ABOUT FAST-FORWARDS" in
git-push(1).
[1 /tmp]$ bzr init trunk
Created a standalone tree (format: 2a)
[2 /tmp]$ (cd trunk && touch foo && bzr add $_ && bzr commit -m X && bzr log --line)
adding foo
Committing to: /tmp/trunk/
added foo
Committed revision 1.
1: Wolfgang Jenkner 2013-12-02 X
[3 /tmp]$ git clone bzr::trunk local
Cloning into 'local'...
Checking connectivity... done
[4 /tmp]$ (cd trunk && echo "trunk change" >foo && bzr commit -m A && bzr log --line)
Committing to: /tmp/trunk/
modified foo
Committed revision 2.
2: Wolfgang Jenkner 2013-12-02 A
1: Wolfgang Jenkner 2013-12-02 X
[5 /tmp]$ (cd local && echo "local change" >foo && git commit -a -m B && git log --oneline && git push)
[master 8b5e5ad] B
1 file changed, 1 insertion(+)
8b5e5ad B
ad0e090 X
Text conflict in foo
1 conflicts encountered.
To bzr::/tmp/trunk
ad0e090..8b5e5ad master -> master
[6 /tmp]$ (cd trunk && bzr log --line)
2: Wolfgang Jenkner 2013-12-02 B
1: Wolfgang Jenkner 2013-12-02 X
[7 /tmp]$ ls -l trunk
total 12
-rw-r--r-- 1 wolfgang wheel 68 Dec 2 16:52 foo
-rw-r--r-- 1 wolfgang wheel 0 Dec 2 16:52 foo.BASE
-rw-r--r-- 1 wolfgang wheel 13 Dec 2 16:52 foo.OTHER
-rw-r--r-- 1 wolfgang wheel 13 Dec 2 16:52 foo.THIS
[8 /tmp]$ cat trunk/foo
<<<<<<< TREE
trunk change
=======
local change
>>>>>>> MERGE-SOURCE
[9 /tmp]$ cat local/foo
local change
[10 /tmp]$ (cd local && git pull)
Already up-to-date.
[11 /tmp]$ git clone bzr::trunk new-local
Cloning into 'new-local'...
Checking connectivity... done
[12 /tmp]$ cat new-local/foo
local change
[13 /tmp]$ (cd trunk && bzr status)
modified:
foo
unknown:
foo.BASE
foo.OTHER
foo.THIS
conflicts:
Text conflict in foo
[14 /tmp]$
next prev parent reply other threads:[~2013-12-03 20:03 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-28 17:32 Latest changes with lisp/uni-*.el and leim/quail Eli Zaretskii
2013-11-28 20:36 ` Glenn Morris
2013-11-29 8:42 ` Eli Zaretskii
2013-11-29 13:46 ` Stefan Monnier
2013-11-29 14:25 ` Eli Zaretskii
2013-11-29 16:43 ` Stefan Monnier
2013-11-29 7:46 ` Dani Moncayo
2013-11-29 8:38 ` Eli Zaretskii
2013-11-29 9:03 ` Dani Moncayo
2013-11-29 20:10 ` Glenn Morris
2013-11-29 21:40 ` Dani Moncayo
2013-11-30 0:37 ` participation & contribution [was: Latest changes with lisp/uni-*.el and leim/quail] Drew Adams
2013-11-30 4:47 ` Jambunathan K
2013-11-30 8:36 ` Eli Zaretskii
2013-11-30 8:43 ` Dani Moncayo
2013-11-30 11:04 ` Eli Zaretskii
2013-11-30 11:11 ` Jarek Czekalski
2013-11-30 23:05 ` Drew Adams
2013-12-01 7:26 ` Thien-Thi Nguyen
2013-12-01 7:27 ` Jambunathan K
2013-12-02 13:29 ` Rüdiger Sonderfeld
2013-12-02 13:37 ` Jarek Czekalski
2013-12-03 10:51 ` Thien-Thi Nguyen
2013-12-03 20:03 ` Wolfgang Jenkner [this message]
2013-12-03 20:33 ` Andreas Schwab
2013-12-03 20:55 ` Wolfgang Jenkner
2013-12-03 21:18 ` Andreas Schwab
2013-12-04 8:50 ` Thien-Thi Nguyen
2013-12-04 10:05 ` Andreas Schwab
2013-12-04 13:52 ` Stefan Monnier
2013-12-04 13:57 ` Andreas Schwab
2013-12-08 11:01 ` adventures w/ git-bzr Thien-Thi Nguyen
2013-12-01 7:50 ` participation & contribution [was: Latest changes with lisp/uni-*.el and leim/quail] Thien-Thi Nguyen
2013-12-01 8:09 ` Jambunathan K
2013-11-30 8:47 ` Jambunathan K
2013-11-30 13:50 ` Stefan Monnier
[not found] <<83txew8m9v.fsf@gnu.org>
[not found] ` <<CAH8Pv0hxmFCoEgd6Wag93LAuNy0JPPJ6UNjt3xcWjNdKAB=K5A@mail.gmail.com>
[not found] ` <<837gbr8uxa.fsf@gnu.org>
[not found] ` <<CAH8Pv0g0P7x=_KOmV2737AJpHgDEJu6_ecdmBseU6rVDuTzKQw@mail.gmail.com>
[not found] ` <<lubo13dl4n.fsf@fencepost.gnu.org>
[not found] ` <<CAH8Pv0h-7J-N-Drhc4vNw=26LtK4YShep0cuDXQeoPjLgqfvoQ@mail.gmail.com>
[not found] ` <<f527b11d-f842-4426-8e41-4991f9abe40c@default>
[not found] ` <<87wqjqts1b.fsf@gmail.com>
[not found] ` <<83zjom5ls5.fsf@gnu.org>
2013-11-30 18:41 ` Drew Adams
2013-12-01 0:05 ` Karl Fogel
2013-12-01 17:39 ` Stephen J. Turnbull
2013-12-01 18:33 ` Karl Fogel
2013-12-01 19:03 ` Stefan Monnier
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=857gblofu0.fsf@iznogoud.viz \
--to=wjenkner@inode.at \
--cc=emacs-devel@gnu.org \
--cc=felipe.contreras@gmail.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).