Junio C Hamano <gitster@xxxxxxxxx> writes: > Han Young <hanyang.tony@xxxxxxxxxxxxx> writes: > >> Changes since v2: >> - rebased to seen: 89afaf27d3 (Merge branch 'ak/typofixes' into seen, 2024-10-10) > > Please NEVER do this. 'seen' is as unstable and fluid as you can get. > > Instead, base it on something that is well known and (supposedly) > stable, like v2.47.0 (or an updated tip of 'master'), and then > test (1) the topic by itself, (2) the result of trial merge of the > topic into 'next', and optionally (3) the same for 'seen'. If your topic really depends on what is done by other topics in-flight, either in 'next' or 'seen', then prepare the base by - picking a well known and stable base, e.g. v2.47.0 - merge these ohter topics in-flight you depend on into the base you chose above and then build your series on top. Remember to describe what you did to prepare the base in your cover letter. Don't directly base your changes to 'next', which would mean your topic will never graduate to 'master', as it is taken hostage by all the topics in 'next' (and the merge commits that merge these topics into 'next', which will never be merged to 'master'). Thanks.
