Greetings all!
I was trying to figure out what the default for Guilt's autotagging feature
should be. Currently, the default is for it to be on, unless it's
overridden by an already existing config setting.
For those who may not be familiar with autotagging, here's an excerpt from
the guilt(7) man page:
Autotagging is a feature that automatically creates unannotated tags
for top, bottom, and base of the stack.
On every push or pop operation (refresh is a pop followed by a
push), Guilt updates the stack top (${branch}_top), stack bottom
(${branch}_bottom), and stack base (${branch}_base) tags.
Top: Top-most applied patch/commit
Bottom: Bottom-most applied patch/commit
Base: Commit on top of which the bottom most patch is applied
Having these three tags, one can easily get the log/diff/other
information only for commits that are (or are not!) part of the
patch stack.
So far the few people (including myself for the past few months) I asked
privately, all said that they turn the feature off.
Ideas? Comments? Suggestions?
Josef 'Jeff' Sipek.
--
I think there is a world market for maybe five computers.
- Thomas Watson, chairman of IBM, 1943.
--
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg Kroah-Hartman | [PATCH 006/196] Chinese: add translation of oops-tracing.txt |
| Eric Sandeen | Re: [RFC] Heads up on sys_fallocate() |
| YOSHIFUJI Hideaki / | request_module: runaway loop modprobe net-pf-1 (is Re: Linux 2.6.21-rc1) |
git: | |
| Gerrit Renker | [PATCH 0/37] dccp: Feature negotiation - last call for comments |
| Jarek Poplawski | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Ben Greear | Re: MACVLANs really best solution? How about a bridge with multiple bridge virtual... |
| Rafael J. Wysocki | 2.6.29-rc8: Reported regressions from 2.6.28 |
