Commit Graph

463 Commits (21b717659eb4060ee87aee003b893ee2ba0bd5cf)

Author SHA1 Message Date
Junio C Hamano 21b717659e Meta/Dothem: pass --locale=* to underlying Meta/Make 2009-04-19 09:06:33 -07:00
Junio C Hamano f355f2565b Meta/Make: allow --locale= and --test= to be given
It often is convenient to run only specific tests while still staying
at the toplevel (some failures only reproduce with particular allocation
patterns, for example).  You can say

    $ Meta/Make --test='1013 91??'

to run only test 1013 and 91xx series.

Similarly, you can give --locale=en_US.UTF-8 or somesuch; earlier we
always run tests in C locale for reproducibility, and the default
stays the same, but sometimes it is useful to run tests in different
locale.
2009-04-19 09:01:41 -07:00
Junio C Hamano 7e8dadd50f Dothem: make it easier to bootstrap 2009-04-19 05:12:57 -07:00
Junio C Hamano 9e9d8b3227 What's cooking 2009-04 #3 2009-04-15 22:46:08 -07:00
Junio C Hamano 1d5c8ccab0 What's cooking 2009-04-15 22:27:26 -07:00
Junio C Hamano dcf14ee007 What's in 2009-04-09 02:10:59 -07:00
Junio C Hamano 366dddbbab What's in 2009-04-09 02:09:41 -07:00
Junio C Hamano 87942e3f49 What's cooking 2009-04-06 01:06:54 -07:00
Junio C Hamano ee7126b8f1 Dothem: no point not installing doc if we build it
It is the building part that is expensive.
2009-04-02 13:01:23 -07:00
Junio C Hamano 958ae8fca9 Make: set ASCIIDOC_NO_ROFF unconditionally for now 2009-04-02 12:13:55 -07:00
Junio C Hamano 6e916ab439 Reintegrate: only detect conflict markers in conflicted files
Otherwise we would misidentify new sections in documentation set
marked with ======= as conflict markers.
2009-04-02 10:19:54 -07:00
Junio C Hamano 411b5ebe48 Dothem: fix dotest/nodoc conditional
The test for nodoc was wrong and also missing from jch branch.
When dotest is not set, make was run twice.  By running make with
just $dotest, we can build either (implicit) all or test.
2009-04-02 10:18:39 -07:00
Junio C Hamano e41c22c7e6 Dothem: Allow nodoc option 2009-03-30 14:42:33 -07:00
Junio C Hamano 34838a2c2e What's cooking/in 2009-03-30 14:42:01 -07:00
Junio C Hamano 7aee035363 Reintegrate: Accept rerere by default 2009-03-30 14:41:37 -07:00
Junio C Hamano 37eea2f665 What's cooking 2009-03-21 00:32:01 -07:00
Junio C Hamano d6aa0d93fe What's in 2009-03-17 22:35:53 -07:00
Junio C Hamano 2efd193a55 Dothem: reset before checking it out again to squelch messages. 2009-03-17 22:29:29 -07:00
Junio C Hamano cc067fafd4 GRADUATED: compare with older maintenance series as well 2009-03-17 22:28:38 -07:00
Junio C Hamano 9948a5150b Announce: typofix 2009-03-17 22:28:07 -07:00
Junio C Hamano f297c5157b What's cooking 2009-03-17 22:27:48 -07:00
Junio C Hamano 140770e990 What's in/cooking 2009-03-14 23:04:30 -07:00
Junio C Hamano 11ac3c74fd Update Dothem to build if jch and next are different 2009-03-12 16:05:56 -07:00
Junio C Hamano fa879484d9 Update Dothem to be more quiet 2009-03-12 16:05:42 -07:00
Junio C Hamano 41ceab1f3f What's cooking 2009-03-11 02:25:58 -07:00
Junio C Hamano a58b4f28b3 What's in -- first mass graduation post 1.6.2 2009-03-06 00:25:38 -08:00
Junio C Hamano 2f8e43af4f Dothem update 2009-03-06 00:24:33 -08:00
Junio C Hamano 61442a7ec3 What's in/cooking 2009-03-05 02:00:48 -08:00
Junio C Hamano 0f6f6ec046 Add Dothem script
This keeps the checkout around and performs much better than Doit.
2009-03-05 01:50:23 -08:00
Junio C Hamano 1c35937ee6 Post 1.6.2 maintnotes updates
Thank new contributors as well.
2009-03-04 11:41:05 -08:00
Junio C Hamano cb9b3a72e5 SE: allow arbitrary send-email options after -- 2009-03-04 11:40:32 -08:00
Junio C Hamano 6ff8635f65 Remove bunch of stale issues - the list is unmaintained these days 2009-03-04 11:40:07 -08:00
Junio C Hamano 4b645ba35d Remove emacsorg-mode list; it seems to be moderated 2009-03-04 11:39:04 -08:00
Junio C Hamano b0eb1eceaa Leftover what's cooking 2009-03-03 01:08:00 -08:00
Junio C Hamano 9eddb0394c What's in 2009-03-03 01:06:58 -08:00
Junio C Hamano c8b60850d0 What's in 2009-03-03 01:01:05 -08:00
Junio C Hamano 9ae0b37c94 What's cooking 2009-02-16 23:55:40 -08:00
Junio C Hamano f68ee0e341 Update Announce for release candidates and use ProjectContact 2009-02-16 23:52:17 -08:00
Junio C Hamano 735f9d11ed Add ProjectContact script 2009-02-16 23:52:02 -08:00
Junio C Hamano c1b07915ae What's in 2009-02-15 02:44:31 -08:00
Junio C Hamano 217580b83e What's cooking 2009-02-15 02:20:22 -08:00
Junio C Hamano dc27452ae4 Reintegrate: sometimes a specific cherry-pick need to be carried forward
This is especially necessary when you reverted a premature merge
to more stable integration branch while you do want to keep the
topic cooking in more experimental integration branch.
2009-02-13 16:56:28 -08:00
Junio C Hamano 61e41ee04e What's in 2009-02-11 20:01:31 -08:00
Junio C Hamano 280195b2cb What's cooking as of 1.6.2-rc0 2009-02-07 13:23:07 -08:00
Junio C Hamano 2c74528332 What's cooking 2009-02-04 17:33:08 -08:00
Junio C Hamano 5ed7079afa What's in update 2009-02-02 00:04:15 -08:00
Junio C Hamano 82b0e7fc7d What's cooking update 2009-02-01 23:39:21 -08:00
Junio C Hamano 24e17294da Add Meta/GRADUATED 2009-01-28 23:52:52 -08:00
Junio C Hamano 2e098204b2 What's in/cooking 2009-01-28 18:01:57 -08:00
Junio C Hamano e97499e1d3 Add Meta/Reintegrate
In a workflow that uses topic branches heavily, you would need to keep
updating test integration branch(es) all the time.  If they are managed
like my 'next' by merging the tips of topics that have grown since the
last integration, it is not so difficult.  You only need to review output
from "git branch --no-merged next" to see if there are topics that can and
needs to be merged to 'next'.

But sometimes it is easier to rebuild a test integration branch from
scratch all the time, especially if you do not publish it for others to
build on.

I've been using this script for some time to rebuild jch and pu branches
in my workflow.  jch's tip is supposed to always match 'next', but it is
rebuilt from scratch on top of 'master' by merging the same topics that
are in 'next'.  You can use the same script in your work.

To use it, you give a commit range base..tip to the script, and you will
see a shell script that uses a series of 'git-merge'.  "base" is the more
stable branch that you rebuild your test integration branch on top (in my
case, 'master'), and "tip" is where the tip of the test integration branch
is from the last round (in my case, 'jch' or 'pu').

Then you can run the resulting script, fix conflicted merge and use
'git-commit', and then repeat until all the branches are re-integrated on
top of the base branch.

    $ Meta/Reintegrate master..jch >/var/tmp/redo-jch.sh
    $ cat /var/tmp/redo-jch.sh
    #!/bin/sh
    while read branch eh
    do
	    case "$eh" in
	    "") git merge "$branch" || break ;;
	    ?*) echo >&2 "Eh? $branch $eh"; break ;;
	    esac
    done <<EOF
    jc/blame
    js/notes
    ks/maint-mailinfo-folded~3
    tr/previous-branch
    EOF
    $ git checkout jch
    $ git reset --hard master
    $ /var/tmp/redo-jch.sh
    ... if there is conflict, resolve, "git commit" here ...
    $ /var/tmp/redo-jch.sh
    ... repeat until everything is applied.

Signed-off-by: Junio C Hamano <gitster@pobox.com>
2009-01-26 00:48:50 -08:00