Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1740164 > unrolled thread
| Started by | Marc Herbert <Marc.Herbert@intel.com> |
|---|---|
| First post | 2017-09-26 21:50 +0200 |
| Last post | 2017-09-27 23:10 +0200 |
| Articles | 3 — 2 participants |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: BUG in git diff-index Marc Herbert <Marc.Herbert@intel.com> - 2017-09-26 21:50 +0200
Re: BUG in git diff-index Eric Wong <e@80x24.org> - 2017-09-26 22:20 +0200
Wrong -dirty suffix set by setlocalversion (was: BUG in git diff-index) Marc Herbert <Marc.Herbert@intel.com> - 2017-09-27 23:10 +0200
| From | Marc Herbert <Marc.Herbert@intel.com> |
|---|---|
| Date | 2017-09-26 21:50 +0200 |
| Subject | Re: BUG in git diff-index |
| Message-ID | <uu41J-zi-29@gated-at.bofh.it> |
On 31/03/16 13:39, Junio C Hamano wrote: > Andy Lowry <andy.work@nglowry.com> writes: > >> So I think now that the script should do "update-index --refresh" >> followed by "diff-index --quiet HEAD". Sound correct? > > Yes. That has always been one of the kosher ways for any script to > make sure that the files in the working tree that are tracked have > not been modified relative to HEAD (assuming that the index matches > HEAD). Too bad kernel/scripts/setlocalversion didn't get the memo: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=cdf2bc632ebc9ef51 > scripts/setlocalversion on write-protected source tree (2013) > I don't see how removing "git update-index" could do any harm. This causes a spurious "-dirty" suffix when building from a directory copy (as Mike learned the hard way) ---- PS: I used NNTP and http://dir.gmane.org/gmane.comp.version-control.git to quickly find this old thread (what could we do without NNTP?). Then I googled for a web archive of this thread and Google could only find this one: http://git.661346.n2.nabble.com/BUG-in-git-diff-index-tt7652105.html#none Is there a robots.txt to block indexing on https://public-inbox.org/git/1459432667.2124.2.camel@dwim.me ?
[toc] | [next] | [standalone]
| From | Eric Wong <e@80x24.org> |
|---|---|
| Date | 2017-09-26 22:20 +0200 |
| Message-ID | <uu4uK-Yn-9@gated-at.bofh.it> |
| In reply to | #1740164 |
Marc Herbert <Marc.Herbert@intel.com> wrote: > PS: I used NNTP and http://dir.gmane.org/gmane.comp.version-control.git > to quickly find this old thread (what could we do without NNTP?). Then > I googled for a web archive of this thread and Google could only find > this one: http://git.661346.n2.nabble.com/BUG-in-git-diff-index-tt7652105.html#none > Is there a robots.txt to block indexing on > https://public-inbox.org/git/1459432667.2124.2.camel@dwim.me ? There's no blocks on public-inbox.org and I'm completely against any sort of blocking/throttling. Maybe there's too many pages to index? Or the Message-IDs in URLs are too ugly/scary? Not sure what to do about that... Anyways, I just put up a robots.txt with Crawl-Delay: 1, since I seem to recall crawlers use a more conservative delay by default: ==> https://public-inbox.org/robots.txt <== User-Agent: * Crawl-Delay: 1 I don't know much about SEO other than keeping a site up and responsive; so perhaps there's more to be done about getting things indexed...
[toc] | [prev] | [next] | [standalone]
| From | Marc Herbert <Marc.Herbert@intel.com> |
|---|---|
| Date | 2017-09-27 23:10 +0200 |
| Subject | Wrong -dirty suffix set by setlocalversion (was: BUG in git diff-index) |
| Message-ID | <uurKG-8gU-5@gated-at.bofh.it> |
| In reply to | #1740164 |
+ linux-kbuild list which is not in the output of: ./scripts/get_maintainer.pl -f scripts/setlocalversion ... but seems relevant anyway. On 31/03/16 13:39, Junio C Hamano wrote: > Andy Lowry <andy.work@nglowry.com> writes: > >> So I think now that the script should do "update-index --refresh" >> followed by "diff-index --quiet HEAD". Sound correct? > > Yes. That has always been one of the kosher ways for any script to > make sure that the files in the working tree that are tracked have > not been modified relative to HEAD (assuming that the index matches > HEAD). Too bad kernel/scripts/setlocalversion didn't get the memo: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=cdf2bc632ebc9ef51 > scripts/setlocalversion on write-protected source tree (2013) > I don't see how removing "git update-index" could do any harm. This causes a spurious "-dirty" suffix when building from a directory copy (as Mike learned the hard way) [...] https://public-inbox.org/git/1459432667.2124.2.camel@dwim.me
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web