All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Stefan Fröberg" <stefan.froberg@petroprogram.com>
To: buildroot@busybox.net
Subject: [Buildroot] Generating patches against packages source code
Date: Sat, 29 Dec 2012 21:04:51 +0200	[thread overview]
Message-ID: <50DF3ED3.60702@petroprogram.com> (raw)
In-Reply-To: <20121229193947.2e157779@skate>

29.12.2012 20:39, Thomas Petazzoni kirjoitti:
> Dear Yann E. MORIN,
>
> On Sat, 29 Dec 2012 19:03:06 +0100, Yann E. MORIN wrote:
>
>> I've found using quilt to be troublesome. For example, you absolutely
>> have to tell quilt what files you are *going* to edit, otherwise,
>> quilt will miss your changes. And this situation happens more often
>> than not; in my experience, it happened quite often that I edited a
>> file because I _knew_ where the failure was, to later find I forgot
>> to tell quilt about that file, and was missing that change in the
>> patch series.
>>
>> So, I would recommend against using quilt; rather use the package's
>> upstream repository, or at worse, create a temporary git tree just in
>> the package's extracted directory: it's much more convenient and
>> powerfull than using quilt.
> <troll severity="strong">
>
> That's because you're using a prehistoric, basic, limited and
> feature-less text editor named vim.
>
> Under the modern, wonderful, feature-rich text editor named Emacs,
> there is something called "quilt-mode". Once you're in quilt mode,
> Emacs turns all buffers of a quilt-managed project read-only, unless
> that particular buffer edits a file that has been quilt-added into the
> current patch.
>
> Therefore, with quilt-mode in place, there is zero chance to
> incorrectly edit a file you forgot to quilt add.
>
> That said, even though I'm an heavy Emacs user, I'm not using
> quilt-mode at the moment. I have been hit often enough with this quilt
> "issue" that I no longer forget to do the quilt add. Or in fact, I
> always use "quilt edit", which makes sure the file is "quilt added"
> before starting up my favorite text editor.
>
> </troll>
>
>  :-)
>
> Thomas

Hope this is not escalating into Vim vs. Emacs flamewar :-)

We "real" programmers just use nano as editor and raw diff as our patch
generating tool.
;-)

From Dilbert comic strip/:

//*Old Guy*:/ When I started out we didn't have those sissy windows and
icons. All we had were zeros and ones./*
Wally:*/ We didn't have ones. I once wrote an entire program with just
zeros./*
Dilbert:*/ You had zeros? We had to use the letter "o".

Stefan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20121229/82c88164/attachment.html>

  reply	other threads:[~2012-12-29 19:04 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-29  1:45 [Buildroot] (no subject) Stefan Fröberg
2012-12-29  1:45 ` [Buildroot] [PATCH 1/5] mesa3d: bumped to 8.0.5 Stefan Fröberg
2012-12-29  8:06   ` Thomas Petazzoni
2012-12-29 13:06     ` Stefan Fröberg
2012-12-29  1:45 ` [Buildroot] [PATCH 2/5] " Stefan Fröberg
2012-12-29  8:07   ` Thomas Petazzoni
2012-12-29  1:45 ` [Buildroot] [PATCH 3/5] " Stefan Fröberg
2012-12-29  8:08   ` Thomas Petazzoni
2012-12-29  1:45 ` [Buildroot] [PATCH 4/5] " Stefan Fröberg
2012-12-29  1:45 ` [Buildroot] [PATCH 5/5] " Stefan Fröberg
2012-12-29  8:08   ` Thomas Petazzoni
2012-12-29  7:59 ` [Buildroot] (no subject) Thomas Petazzoni
2012-12-29 14:13   ` Stefan Fröberg
2012-12-29 14:32     ` Thomas Petazzoni
2012-12-29 14:56       ` Stefan Fröberg
2012-12-29 15:23         ` [Buildroot] (no subject) git format-patch Carsten Schoenert
2012-12-29 15:31           ` Stefan Fröberg
2012-12-29 16:15         ` [Buildroot] Generating patches against packages source code Thomas Petazzoni
2012-12-29 16:54           ` Stefan Fröberg
2012-12-29 17:09             ` Richard Braun
2012-12-29 17:13               ` Thomas Petazzoni
2012-12-29 17:33                 ` Richard Braun
2012-12-29 18:03           ` Yann E. MORIN
2012-12-29 18:39             ` Thomas Petazzoni
2012-12-29 19:04               ` Stefan Fröberg [this message]
2012-12-29 19:56                 ` Yann E. MORIN
2012-12-29 20:18                   ` Stefan Fröberg
2012-12-29 19:52               ` Yann E. MORIN

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=50DF3ED3.60702@petroprogram.com \
    --to=stefan.froberg@petroprogram.com \
    --cc=buildroot@busybox.net \
    /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.