grub-devel.gnu.org archive mirror
 help / color / mirror / Atom feed
From: "Aleš Nesrsta" <starous@volny.cz>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: [PATCH] USB Mass Storage CBI support
Date: Sat, 02 Oct 2010 23:25:21 +0200	[thread overview]
Message-ID: <1286054722.6453.23.camel@pracovna> (raw)
In-Reply-To: <4CA62A4E.5090008@gmail.com>

Vladimir 'φ-coder/phcoder' Serbinenko wrote:
> >> Other that this it can be merged into experimental. Be sure to push
> >> branches/cbi and then merge branches/cbi into experimental

Hi,

it is done.
But I am not 100% sure if I did it correctly - there is list what I did
(I hope according to your suggestions):

1. I made cbi branch from trunk
2. I applied CBI patch to cbi repository and committed changes
3. I pushed cbi repository to
bzr.savannah.gnu.org/srv/bzr/grub/branches/cbi
4. I merged cbi into experimental branch, commited changes and pushed.
And there could be problem. Changes listed during merging were:
 M  ChangeLog
 M  grub-core/bus/usb/ohci.c
 M  grub-core/bus/usb/uhci.c
 M  grub-core/bus/usb/usbtrans.c
 M  grub-core/disk/usbms.c
 M  grub-core/loader/i386/linux.c
 M  grub-core/term/efi/console.c
 M  include/grub/scsi.h
No problem with ohci.c, uhci.c, usbtrans.c, usbms.c, scsi.h (my changes)
and probably no problem with ChangeLog (it is probably not critical in
experimental branch - or ?). But what about replacing files "linux.c"
and "console.c" - is it correct ? (I can imagine these files have older
version in trunk - or is it not possible ?)

Regards
Ales



      reply	other threads:[~2010-10-02 21:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-26 20:11 [PATCH] USB Mass Storage CBI support Aleš Nesrsta
2010-09-30 21:08 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-10-01 15:06   ` Aleš Nesrsta
2010-10-01 18:37     ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-10-02 21:25       ` Aleš Nesrsta [this message]

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=1286054722.6453.23.camel@pracovna \
    --to=starous@volny.cz \
    --cc=grub-devel@gnu.org \
    /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 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 NNTP newsgroup(s).