All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christopher Li <sparse@chrisli.org>
To: Dibyendu Majumdar <mobile@majumdar.org.uk>
Cc: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>,
	Linux-Sparse <linux-sparse@vger.kernel.org>
Subject: Re: Upcoming sparse release RC5
Date: Wed, 9 Aug 2017 20:18:31 -0400	[thread overview]
Message-ID: <CANeU7Q=w3REgmDDQ-t6LyWrnOijqcxnokr3AjCC4Rqk3x7ZmvA@mail.gmail.com> (raw)
In-Reply-To: <CACXZuxd83EjbX5i9cgo0H3TTNKBV+pHec7HURVb2GF-GJOFszQ@mail.gmail.com>

On Wed, Aug 9, 2017 at 5:10 AM, Dibyendu Majumdar
<mobile@majumdar.org.uk> wrote:
>
> I think that compile error should not be possible? Because before you
> merge any patch presumably you build Sparse and run the tests?
>
> As for other changes that were later removed - in my view this is
> valuable history as it tells people what was tried and discarded and
> why. I still feel all history is good.
>

OK. I think my obsession of "clean up the history" is wrong and not  worthy
doing. Linus's criticism of sparse-next rebase is correct.  I will just got back
to the master doing the normal git pull and merges. That actually simplify
my own work flow as we.

Chris

  reply	other threads:[~2017-08-10  0:18 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-05 15:46 Upcoming sparse release RC5 Christopher Li
     [not found] ` <CACXZuxdLX3r+LrhBJYnC54HZhTN152JkPZAQGqhoQwEFjcyiYw@mail.gmail.com>
2017-08-05 16:16   ` Fwd: " Christopher Li
2017-08-05 22:32 ` Luc Van Oostenryck
2017-08-05 22:50   ` Christopher Li
2017-08-07 16:41     ` Luc Van Oostenryck
2017-08-07 23:32       ` Christopher Li
2017-08-07 23:58         ` Luc Van Oostenryck
2017-08-08  0:23         ` Luc Van Oostenryck
2017-08-08  0:42           ` Christopher Li
2017-08-08  0:58             ` Luc Van Oostenryck
2017-08-08  1:34               ` Christopher Li
2017-08-08  1:43                 ` Luc Van Oostenryck
2017-08-08  2:13                 ` Luc Van Oostenryck
2017-08-08  2:38                   ` Christopher Li
2017-08-08  3:31                     ` Linus Torvalds
2017-08-08  4:43                       ` Christopher Li
2017-08-10  0:24                       ` Christopher Li
2017-08-08 12:02                     ` Luc Van Oostenryck
2017-08-08 13:44                       ` Christopher Li
2017-08-08 16:10                         ` Dibyendu Majumdar
2017-08-08 19:03                           ` Christopher Li
2017-08-09  9:10                             ` Dibyendu Majumdar
2017-08-10  0:18                               ` Christopher Li [this message]
2017-08-10  0:42                                 ` Dibyendu Majumdar
2017-08-10  1:01                                   ` Christopher Li
2017-08-09  0:40                         ` Luc Van Oostenryck
2017-08-07  2:06   ` Christopher Li
2017-08-07  8:07     ` Luc Van Oostenryck

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='CANeU7Q=w3REgmDDQ-t6LyWrnOijqcxnokr3AjCC4Rqk3x7ZmvA@mail.gmail.com' \
    --to=sparse@chrisli.org \
    --cc=linux-sparse@vger.kernel.org \
    --cc=luc.vanoostenryck@gmail.com \
    --cc=mobile@majumdar.org.uk \
    /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.