linux-kernel - Re: [GIT PULL] regulator fixes for v3.15

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CA+55aFznxvzfqa7OM0VoQ337kVYQ0hSjkqC26sxv7mxBuX9J-Q@mail.gmail.com>
Date:	Fri, 11 Apr 2014 13:30:08 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Mark Brown <broonie@...nel.org>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Liam Girdwood <lgirdwood@...il.com>
Subject: Re: [GIT PULL] regulator fixes for v3.15

On Fri, Apr 11, 2014 at 3:38 AM, Mark Brown <broonie@...nel.org> wrote:
>
> Due to the way my scripts incorporate the things I already sent since
> your last tag the diffstat has picked up all the changes already sent
> (or I could've generated against my previous pull when it'd show all the
> changes from the final -rc to release).  I will look into fixing that,
> please let me know if it's an immediate problem.

Not an immediate problem, but have you tested just adding a simple
"git fetch" from my repo to your scripts?

Note the "fetch". Not "pull". No merging going on, just updating your
remote branch information with what is in my tree. Then you can just
tell git to generate the report based on that information - never
actually needing to update your own branches at all, or touching your
own development state.

              Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/