From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>,
Robert Millan <rmh@aybabtu.com>
Subject: [URGENT] Re: bazaar
Date: Mon, 23 Nov 2009 02:19:24 +0100 [thread overview]
Message-ID: <4B09E31C.7070207@gmail.com> (raw)
In-Reply-To: <20091123004418.GA14340@pina.cat>
[-- Attachment #1: Type: text/plain, Size: 2319 bytes --]
Carles Pina i Estany wrote:
> Hello,
>
> I have to go to sleep now, but I've realized about a mistake or at least
> unexpected behaviour.
>
> After merging trunk with people/carles/gettext as Robert said I have been
> committing and pushing a couple of things to people/carles/gettext. But I think
> that after I merged it trunk now is always merged with carles/gettext .
>
> revno 1848 and 1849 in trunk are pushes to my branch (or at least this
> was my intention). After a clean checkout from trunk, doing bzr log:
>
> ------------------------------------------------------------
> revno: 1849
> committer: Carles Pina i Estany <carles@pina.cat>
> branch nick: carlesgettext
> timestamp: Sun 2009-11-22 23:41:06 +0000
> message:
> 2009-11-22 Carles Pina i Estany <carles@pina.cat>
>
> * normal/menu_text.c (get_spaces): New function.
> (print_timeout): Gettextize, add spaces to the localized string.
> ------------------------------------------------------------
> revno: 1848
> committer: Carles Pina i Estany <carles@pina.cat>
> branch nick: carlesgettext
> timestamp: Sun 2009-11-22 22:24:54 +0000
> message:
> 2009-11-22 Carles Pina i Estany <carles@pina.cat>
>
> * normal/menu_text.c: Gettexttize but not print_timeout function.
> * normal/main.c: Gettexttize.
> * normal/menu_entry.c: Likewise.
> ------------------------------------------------------------
>
> 1848 should be fine but I sent some hours ago a mail to discuss and
> confirm it. So we should check, etc. 1849 is a file to track my changes
> but not in trunk
>
> How we proceed? Should I stop working with people/gettext ?
> Should we "unmerge" and merge?
>
> Thank and apologizes for the bazaar messes ups,
>
>
Looks like the mess is actually more profound than you describe. You
replaced our mainstream with your branch. Looks like bzr failed at its
primary task: protect against unintentional or intentional deletion of
files. We should think of a way to make trunks and experimental branch
commit-only. Meanwhile nobody pushes until further notice. I'll see how
it can be recovered and protected.
Robert: What is your latest backup before this accidental replacement?
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 293 bytes --]
next prev parent reply other threads:[~2009-11-23 1:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-23 0:44 bazaar Carles Pina i Estany
2009-11-23 1:19 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2009-11-23 1:40 ` [ISSUE SOLVED] bazaar Vladimir 'φ-coder/phcoder' Serbinenko
2009-11-23 9:33 ` Robert Millan
2009-11-23 9:59 ` Carles Pina i Estany
2009-11-23 10:30 ` Robert Millan
2009-11-23 12:01 ` Vladimir 'φ-coder/phcoder' Serbinenko
2009-11-23 9:35 ` Robert Millan
2009-11-24 15:50 ` [URGENT] " Colin D Bennett
2010-01-07 18:53 ` Robert Millan
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=4B09E31C.7070207@gmail.com \
--to=phcoder@gmail.com \
--cc=grub-devel@gnu.org \
--cc=rmh@aybabtu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.