[PATCH] vsprintf: fix build warning

[PATCH] vsprintf: fix build warning

[Tobin C. Harding]

CC'ing kernel newbies for anyone else trying to learn how linux-next
works.

On Fri, Jul 06, 2018 at 11:49:51AM -0400, Steven Rostedt wrote:
> On Fri, 6 Jul 2018 23:42:13 +0900
> Sergey Senozhatsky <sergey.senozhatsky@gmail.com> wrote:
> 
> > On (07/06/18 15:47), Arnd Bergmann wrote:
> > [..]
> > > Fixes: bfe80ed3d7c7 ("vsprintf: add command line option debug_boot_weak_hash")  
> > 
> > Seems like this one is still in linux-next.
> > Can we squash this patch and bfe80ed3d7c7?
> > 
> 
> I prefer not to do squashes unless absolutely necessary. Yes, it is in
> next, but even branches pulled into next should try to resist rebasing
> (I never rebase my next branch unless there is a real bug that will
> break bisecting).

Steve if you do not rebase your next branch and the branch ends up
containing fixes to patches like the above doesn't this mean that when
you do a pull request to Linus the branch you are asking to be pulled
will be too 'dirty' i.e. I thought that the pull request should be like
a patch set and only contain the 'final product' not every change that
was made during development?

I was under the impression that each maintainer constantly rebased their
next branches and that was why one has to checkout the tagged linux-next
each day instead of just pulling.  From information on the net somewhere
I have been checking out linux-next using this shell function

checkout-next () {
	local branch='linux-next' 

	git checkout master
	git remote update linux-next
	git branch -D $branch
	git checkout -b $branch $(git tag -l "next-*" | tail -1)
}

Also, when my leaks tree got included in linux-next I was told that it
was ok to rebase and have since been rebasing mercilessly.


thanks in advance for your time,
Tobin.

[PATCH] vsprintf: fix build warning

[Sergey Senozhatsky]

On (07/10/18 09:42), Tobin C. Harding wrote:
> > I prefer not to do squashes unless absolutely necessary. Yes, it is in
> > next, but even branches pulled into next should try to resist rebasing
> > (I never rebase my next branch unless there is a real bug that will
> > break bisecting).
> 
> Steve if you do not rebase your next branch and the branch ends up
> containing fixes to patches like the above doesn't this mean that when
> you do a pull request to Linus the branch you are asking to be pulled
> will be too 'dirty' i.e. I thought that the pull request should be like
> a patch set and only contain the 'final product' not every change that
> was made during development?

+1

	-ss

[PATCH] vsprintf: fix build warning

[Steven Rostedt]

On Tue, 10 Jul 2018 09:42:03 +1000
"Tobin C. Harding" <me@tobin.cc> wrote:

> Steve if you do not rebase your next branch and the branch ends up
> containing fixes to patches like the above doesn't this mean that when
> you do a pull request to Linus the branch you are asking to be pulled
> will be too 'dirty' i.e. I thought that the pull request should be like
> a patch set and only contain the 'final product' not every change that
> was made during development?

Nope, once I push to next, my branch is ready to be worked against.
Sha1 and all. Rebasing will break that. I also have a full test suite
that all my code runs through and it must pass before sending to Linus
or linux-next.

> 
> I was under the impression that each maintainer constantly rebased their
> next branches and that was why one has to checkout the tagged linux-next

Some maintainers (Ingo being one) is very against any unnecessary
rebasing. This is because it can hide the history and development of
code. Linus doesn't like to see rebasing of public trees. Once you
rebase, you lose all the prior testing done on the previous code. It
also makes it difficult for anyone that is basing code off of it.

> each day instead of just pulling.  From information on the net somewhere
> I have been checking out linux-next using this shell function
> 
> checkout-next () {
> 	local branch='linux-next' 
> 
> 	git checkout master
> 	git remote update linux-next
> 	git branch -D $branch
> 	git checkout -b $branch $(git tag -l "next-*" | tail -1)
> }

I believe linux-next itself creates its master branch each time it
pulls in everyone's branches. It throws away the old one, and pulls in
all the new ones. This makes sense because otherwise the history will be
loaded with pulls from various branches. And yes, some branches will
rebase. If just one branch rebases, then it would need to do this.

> 
> Also, when my leaks tree got included in linux-next I was told that it
> was ok to rebase and have since been rebasing mercilessly.

It's really a choice for the maintainer. I consider a branch that goes
into next as "tested". I wont rebase unless there is a nasty bug that I
don't want to go upstream. Or a compiler failure. Warnings don't bother
me. I've sometimes rebased to add Acked-by/Reviewed-by tags. But that's
because the code is identical to what was there before (I do git diffs
to confirm that).

Linus has yelled at people that have rebased just before sending a
pull request to him.

-- Steve

[PATCH] vsprintf: fix build warning

[valdis.kletnieks at vt.edu]

On Tue, 10 Jul 2018 09:42:03 +1000, "Tobin C. Harding" said:

> I was under the impression that each maintainer constantly rebased their
> next branches and that was why one has to checkout the tagged linux-next
> each day instead of just pulling.

Close, but no cigar.  The maintainers don't rebase their -next branches, but
due to the way linux-next merges 200+ trees on top of current Linus tree,
*that* ends up rebasing every day.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 486 bytes
Desc: not available
URL: <http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20180709/7c28ed2e/attachment.sig>