public inbox for frysk@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Cagney <cagney@redhat.com>
To: Kris Van Hees <kris.van.hees@oracle.com>
Cc: frysk <frysk@sources.redhat.com>
Subject: Re: 32-64 branch?
Date: Wed, 20 Jun 2007 13:23:00 -0000	[thread overview]
Message-ID: <4679246A.4080308@redhat.com> (raw)
In-Reply-To: <20070619224752.GE3085@ca-server1.us.oracle.com>

Kris,

Branching is cheap (even allowing for CVS); and it lets us cite the code 
base against which discussion was held.  I can always cut one myself.

Andrew

Kris Van Hees wrote:
> I'd typically do that because it is indeed the easiest way to ensure
> that you can access the same source code.  In this case however I think
> it is major overkill, because the changes are minimal.  I'll be posting
> a diff that can be fed to patch prior to the meeting so everyone will
> have the minimal changes.  It's really just enabling the two windows so
> the problems with them can be demonstrated.
>
> 	Cheers,
> 	Kris
>
> On Tue, Jun 19, 2007 at 06:37:16PM -0400, Andrew Cagney wrote:
>   
>> Kris,
>>
>> On IRC you mentioned:
>>
>> Jun 19 15:11:15 SqRoot  mjw: For tomorrow's meeting, we won't be able to 
>> use a std frysk build due to the two particular windows being disabled 
>> on x86_64, and it needing an x86_64 either way to show the problems.
>>
>> can I suggest cutting a branch and putting the changes there?  That way 
>> we can access them and build locally if needed.
>>
>> Andrew
>>
>>     

      reply	other threads:[~2007-06-20 12:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-19 22:48 Andrew Cagney
2007-06-20  1:35 ` Kris Van Hees
2007-06-20 13:23   ` Andrew Cagney [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=4679246A.4080308@redhat.com \
    --to=cagney@redhat.com \
    --cc=frysk@sources.redhat.com \
    --cc=kris.van.hees@oracle.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 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).