> There is no staging area. That's actually a deal breaker to me. Effectively using Git's staging area has become so integral to the way I work with repositories that I don't think I can ever go back to the old style.
[deleted]
Sapling: A new source control system with Git-compatible client
191–200 of 543 posts
Re: Sapling: A new source control system with Git-compatible client
#192Earlier quoted context omitted.
Lol. Orrr we could just do things sensibly in the first place.
I always chuckle when things like “sensible”, “user-friendly” or “sane” get thrown around as if they are anything more than that person’s opinion. When are developers going to learn that they actually have to learn and familiarize themselves with preexisting systems, instead of endlessly reinventing them, and that there is no such thing as the perfect system?
Nothing is perfect, but some things are clearly better than others - hence why we’re nearly-all using git rather than "learning and familiarising ourselves" with CVS :)
Re: Sapling: A new source control system with Git-compatible client
#193FYI, as-shared at Meta: > First things first, please go to your phone and turn off wifi to avoid voter ring detection and upvote us on Hacker News!
[deleted]
Re: Sapling: A new source control system with Git-compatible client
#194Re: Sapling: A new source control system with Git-compatible client
#195Earlier quoted context omitted.
Weird, it's one of my favorite changes. Finally I might get a version of Git which works without a bunch of extra crap getting in my way! you can always just use another commit as a staging area, I figure, and it'll make all the commands simpler and more intuitive so it wins in my book.
> you can always just use another commit as a staging area, And than you have to do gymnastics with rebasing and rewriting history afterwards. Using the staging area upfront is much simpler!
Oh well, I don't have any problem with that. I like having all my changes always committed though.
Re: Sapling: A new source control system with Git-compatible client
#196Add Comment
Re: Sapling: A new source control system with Git-compatible client
#197Earlier quoted context omitted.
I felt the same joy on reading the overview. Cleans up the git workflow so nicely. ...until I got to pull requests (Granted, that is github, not git). But it looks like you cannot generate a standard pull request with it. https://sapling-scm.com/docs/git/intro#pull-requests Haven’t tried it yet, looking forward to it.
I actually just created my first PR from a sapling repo now - not sure why it’s not documented, but you can push your local development branch to a remote server, and in the case of github, you even get the “it looks like you’ve just pushed a local branch, would you like to turn this branch into a PR?” prompt, and it appears indistinguishable from a branch created with the Git CLI.
The message generated with the hyperlink for creating a PR is actually done server-side, you can customize any git server to do this, more or less. So yes, it should behave approximately the same assuming you can just do the basic push interactions.
Re: Sapling: A new source control system with Git-compatible client
#198Thank god. I have been waiting ten years ( https://www.google.com/url?q=https://stevebennett.me/2012/02... ) for someone to develop a better CLI for git, someone with the scale and clout to do it well and gain mindshare. It's not that useful to learn a new workflow if no one you ever work with will be familiar with it. This looks incredible. A simple command to uncommit or unamend makes you further realise what a dis…
Forget the CLI. VSCode implements a ton of git features as commands, which can be bound to any keybindings. For me this is way faster than CLI, as I don’t even need to leave my text editor - I have it set up chorded, so AltG followed by P,U,C,Y, will push (actually sync), pull, commit, undo, respectively. Two keystrokes beats any CLI interaction I’ve seen.
(Disclaimer used to make VSCode)
Re: Sapling: A new source control system with Git-compatible client
#199Earlier quoted context omitted.
I always chuckle when things like “sensible”, “user-friendly” or “sane” get thrown around as if they are anything more than that person’s opinion. When are developers going to learn that they actually have to learn and familiarize themselves with preexisting systems, instead of endlessly reinventing them, and that there is no such thing as the perfect system?
Nothing is perfect, but some things are clearly better than others - hence why we’re nearly-all using git rather than "learning and familiarising ourselves" with CVS :)
Fair point, but it is not clear to me that Sapling is better than Git. I haven’t seen anything in its docs or in the comments here where I haven’t thought of a way to do it with Git.
I wonder what the cost benefit analysis would be: how many developers hours have been expended building Sapling so far, vs a list of things it can do that Git cannot.
And I guess it bears repeating that I’m interested in possibility and not aesthetics.
Re: Sapling: A new source control system with Git-compatible client
#200FYI, as-shared at Meta: > First things first, please go to your phone and turn off wifi to avoid voter ring detection and upvote us on Hacker News!
Because people on the internal network are behind the same ip address(es)... This makes perfect sense to mention that while showcasing work. I'm not sure what are you insinuating.