2008/6/30 Noah Kantrowitz <[EMAIL PROTECTED]>:

>
> On Jun 30, 2008, at 4:49 PM, Endre Bakka wrote:
>
> >
> >> You mean git puts the patch content inline?
> >
> > Yes, git puts it inline. This is the preferred way of submitting
> > changes
> > to e.g. the Linux kernel (preferred as in everything else will be shot
> > down in flames ;-)) - when discussing changes on a mailing list it
> > can be
> > handy.
> >
>
Ack!  Thank goodness I'm not listening in on or involved with any Linux
development.  Remind me to put a match under that list and fan the flames,
so that it can burn-baby-burn!
Spamming a list with that volume of text has been considered very very bad
form for a very very long time.  [showing my age]


> > Note that git also automatically pulls patches from your mailbox and
> > applies them making it quite convenient. Just 'git am':
> >
> > http://www.kernel.org/pub/software/scm/git/docs/git-am.html
>
> Get it working with either Mail.app mailboxes or IMAP and we will
> talk ;-)
>
> I suppose I could make some applescript that reads the text from the
> message and pipes it to get, but that is getting far more complicated
> than "Click patch"->"run patch -p0 <~/Downloads/..."->restart server


Quite...  not exactly operating system agnostic.

Trac has a very good way of managing bug/enhancement/task requests and files
associated with those those requests.  Post a ticket and invite discussion.
Don't send hundreds of patch lines to a mailing list. ;)

Stephen

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac 
Development" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/trac-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to