"Martin v. Löwis" writes: > Am 22.03.2011 02:02, schrieb Eugene Toder: > >> Not if the changes you want to suppress are actually also on the same > >> branch as the one whose mainline you are trying to see (which they > >> typically are, with the branch typically being "default"). > > > > Right, that would amount to not using named branches. But if you > > develop on a named feature-branch and merge into "default" when ready > > your local history is easy to filter-out without rebasing or > > collapsing. > > Ah. We don't support this kind of development - no new named branches > are allowed in the central repository. Maybe it would be possible to allow *closed* named branches, which would support such filtering.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4