On Tue, Jan 19, 2010 at 09:51:21AM +0530, BVK Chaitanya wrote:
>
> I haven't seen anybody sending "bzr send" patches in the ML, so I
> didn't want to introduce something new.
Please don't let this stop you if you think "bzr send" is useful. Most
of us are relatively new to Bazaar, so we might be
On Mon, Jan 18, 2010 at 12:48:56PM -0800, Colin D Bennett wrote:
>
> I mainly afraid of trunk checkouts because it tempts people to
> actually make code changes directly in the checkout,
I think this is fine for small changes. Bigger efforts can easily use a
branch (either local or published) an
2010/1/19 Colin D Bennett :
> On Tue, 19 Jan 2010 11:52:27 +0100
> Michal Suchanek wrote:
>
>> 2010/1/19 BVK Chaitanya :
>> > On Mon, Jan 18, 2010 at 11:19 PM, Colin D Bennett
>> > wrote:
>>
>> >>>
>> >>> # create a patch and send to mailing list
>> >>> grub$ bzr diff -r submit: > ~/my-issue-fix.
On Tue, 19 Jan 2010 11:52:27 +0100
Michal Suchanek wrote:
> 2010/1/19 BVK Chaitanya :
> > On Mon, Jan 18, 2010 at 11:19 PM, Colin D Bennett
> > wrote:
>
> >>>
> >>> # create a patch and send to mailing list
> >>> grub$ bzr diff -r submit: > ~/my-issue-fix.diff
> >>
> >> Why not use “bzr send -o
On Tue, Jan 19, 2010 at 09:57:07AM +0530, BVK Chaitanya wrote:
> On Mon, Jan 18, 2010 at 11:45 PM, Colin Watson wrote:
> > I recommend using a checkout for trunk, because that way bzr takes out a
> > write lock on the branch when you start committing and doesn't release
> > it until it's finished;
2010/1/19 BVK Chaitanya :
> On Mon, Jan 18, 2010 at 11:19 PM, Colin D Bennett wrote:
>>>
>>> # create a patch and send to mailing list
>>> grub$ bzr diff -r submit: > ~/my-issue-fix.diff
>>
>> Why not use “bzr send -o ~/my-issue-fix.patch” to create a merge
>> directive+patch+revision bundle? Th
On Mon, Jan 18, 2010 at 11:45 PM, Colin Watson wrote:
>
> I recommend using a checkout for trunk, because that way bzr takes out a
> write lock on the branch when you start committing and doesn't release
> it until it's finished; it also warns you immediately if you're out of
> date rather than ma
On Mon, Jan 18, 2010 at 11:19 PM, Colin D Bennett wrote:
>>
>> * For Occasional Contributors
>>
>> This workflow is recommended for users/developers who want to fix
>> just-one GRUB issue. This involves a trunk checkout, some local
>> commits (as necessary for fixing the issue) and sending the pa
On Mon, 18 Jan 2010 18:15:37 +
Colin Watson wrote:
> On Mon, Jan 18, 2010 at 09:49:15AM -0800, Colin D Bennett wrote:
> > Do you want to mention how GRUB committers should merge features to
> > the official trunk branch? I think the appropriate process,
> > assuming (1) either a merge direct
On Mon, Jan 18, 2010 at 09:49:15AM -0800, Colin D Bennett wrote:
> Do you want to mention how GRUB committers should merge features to the
> official trunk branch? I think the appropriate process, assuming
> (1) either a merge directive or a feature branch provides the change
> the we want to merg
On Thu, 14 Jan 2010 15:01:41 +0530
BVK Chaitanya wrote:
> Hi,
>
>
> Attached is the initial version of workflow document for GRUB
> contributions. I am yet to get right DVCS right, so I suspect it
> might have minor differences from what other developers are following
> already.
>
> Let me kn
BVK Chaitanya wrote:
Attached is the initial version of workflow document for GRUB
contributions. I am yet to get right DVCS right, so I suspect it
might have minor differences from what other developers are following
already.
I can't comment on details, but thank you for this. It is very he
Hi,
Attached is the initial version of workflow document for GRUB
contributions. I am yet to get right DVCS right, so I suspect it
might have minor differences from what other developers are following
already.
Let me know your comments.
--
bvk.chaitanya
GNU GRUB Workflow
GNU GRUB project re
13 matches
Mail list logo
