Birbla

Join the discussion

Write your take first — we'll ask for email only when you're ready to publish.

Sign in
  • Hacker News
  • Perhaps I'm missing something (it's been a long day), but couldn't "--" be used for both?

        git cmd --options -- rev -- pathspec
    would be the fully specified revspec and pathspec

        git cmd --option -- rev --
    would be just the revspec, excluding accidental options, without a pathspec

        git cmd --option revspec -- pathspec
    and the single "--" would work as it currently does.
    by epistasis
  • This is actually one of the few places powershell begins to do something close to shine - the cli mixes data and commands in a way that we really shouldn't have to do.

    The saddest thing is even ASCII has characters to help with this but since keyboards can't type them nobody used them.

    by bombcar
  • > git log --end-of-options "$rev" -- "$path",

    Argh, that's when I wished for object oriented shells. Powershell sure isn't perfect but objects encoding their own meaning really helps differentiate those cases (but it may not always help the user if types aren't clear to the reader)

    by _blk
  • The "Everything is text, do everything via text" philosophy has its advantages, and also its disadvantages.
    by Chinjut
  • As with almost any successful system: more and more special features and edge cases get added. Git has become ridiculously complex.

    I wonder: would it not be better to tell users with those edge cases to fix their problems some other way? To take an example from the article: why does someone have a filename beginning with a dash? Maybe don't do that.

    by bradley13
  • So I should name my next branch ‘--‘ is what I'm hearing :)
    by yobert
  • Does anyone know why git broke the long standing convention of "--" early on? Kind of a nightmare for humans to use.

    Remembering app-specific one-offs is kind of the worst!

    by metadat

Explore Birbla archives