Was: [Mystery solved, I owe you an apology] (was: [git-users] how to
remove two commits from a remote server)
On Wed, Dec 1, 2021 at 12:18 PM Uwe Brauer wrote:
> As I said I am one of the maintainer of
> matlab-mode(emacs), a git repository in sourceforge. Since I know
> mercurial relatively
On Sun, Aug 29, 2021 at 3:51 AM SJW wrote:
> I will regularly create feature branches for each new enhancement or fix.
> The problem rears its head when testing is delayed and the first feature
> (feature-branch-1) is still not approved for production and sits as a
> branch awaiting merge.
>
>
On Fri, 18 Oct 2019 at 11:59, Benjamin wrote:
> This could be an issue of git. The exact steps to reproduce this issue are
> as below,
>
> $git merge master
> ...
>$git rebase -i e705c6a dev1 # e705c6a is the ancestor commit of
> branch dev1
>In the interactive rebase page, Keep
On Wed, 15 May 2019, 14:04 Giorgio Forti, wrote:
> I'm relatively new to Git.
> I use it from inside Visual Studio 2013, for the normal operations:
> commit, push ...
> I used and know other similar products but not Git.
> I'm searching in Git a feature I used in the past in another product.
>
>
On Fri, 26 Apr 2019, 04:22 ckdev101, wrote:
>
> Here is the team make-up:
>
>- Sprint Team #1
>- Sprint Team #2
>- *Shared* DBA across teams
>- Dev. Lead (Myself)
>
> ...
>
> The problem is that the shared DBA needs to constantly and consistently
> make changes *across* teams for
On Sun, 7 Apr 2019, 20:46 , wrote:
>
> In the while, I come back to my original question: what is *--merge* command
> line option of *git rebase* command?
>
Unless you have changed your default merge strategy that option does
nothing if I've understood correctly. As far as I know, the rebase
On Sun, 7 Apr 2019, 20:46 , wrote:
>
>- ... however how to undo a rebasing (if possible) will be a future
>deepening of mine,
>
> Rebase always creates technically new commits instead of replacing old
commits. You can simply hard reset your branch wherever you want. Command
"git reflog
On Fri, Nov 18, 2011 at 07:11, PJ Weisberg p...@irregularexpressions.net
wrote:
I'm looking for something in Git analogous to the revision numbers in
Subversion. Pretty much exactly what you get from `git describe', but
I don't want it to be dependent on any tags or refs. Is there any way
