On 19.07.22 10:32, Uwe Brauer wrote:
Isn't it what you are proposing, what mercurial would call
a «named branch»?
… and couldn't you just tag the feature branch "feature/FUBAR" before
merging, thereby accomplishing much the same thing?
--
-- regards
--
-- Matthias Urlichs
--
You received
On 24.01.22 10:53, Konstantin Khomoutov wrote:
Yes: setting both core.autocrlf to "false" and core.eol to "crlf"
should defeat Git's EOL normalizations.
The problem is that I don't want to defeat it. I want to apply it in the
other direction.
My problem is: the project I'm working on
On 02.11.19 16:20, Konstantin Khomoutov wrote:
> how does it become
> superior to a VCS by storing snapshots rather than deltas?
Deltas based on what? As soon as there are merge operations, you either
run into ambiguities or the code is forced to prefer one branch over the
other. Branches and
On 03.11.18 09:40, j...@tcs.ifi.lmu.de wrote:
> @Matthias Urlichs: The file had been comitted to the repository
> initially. It was only added to .gitignore much later on, when other
> users complained.
Ah. Sorry, I missed that.
You're right – this is a bug. My reasoning for that assessment is
On 02.11.18 18:12, j...@tcs.ifi.lmu.de wrote:
> The file is heavily edited, but ignored by commits as expected.
Last time I checked (which was half a minute ago), files in .gitignore
are only ignored for the purpose of not adding them to the archive.
Modifying such a file, editing it, and then
