Federati Nu: Federated N-series GNU Social
  • Login
It's "All Of Us For All Of Us" Or We're On Our Own

  • Public

    • Public
    • Groups
    • Popular
    • People

Notices tagged with git

  1. Claes Wallin 🇸🇪🇭🇰 (clacke@libranet.de)'s status on Saturday, 06-Nov-2021 14:13:11 UTC Claes Wallin 🇸🇪🇭🇰 Claes Wallin 🇸🇪🇭🇰
    Remote profile options...
    A minimal example of a merge that darcs and pijul will get right, but svn and git will get wrong: tahoe-lafs.org/%7Ezooko/badmer…

    #darcs #pijul #svn #git
    In conversation about a month ago from libranet.de permalink
  2. Claes Wallin 🇸🇪🇭🇰 (clacke@libranet.de)'s status on Tuesday, 14-Sep-2021 04:39:16 UTC Claes Wallin 🇸🇪🇭🇰 Claes Wallin 🇸🇪🇭🇰
    Remote profile options...
    oh wow this is super useful
    > --fixup=reword:<commit> creates an "amend!" commit which replaces the log message of <commit> with its own log message but makes no changes to the content of <commit>.
    git-scm.com/docs/git-commit#Do…

    #git #gitRebase #gitFixup #gitAutosquash
    In conversation about 3 months ago from libranet.de permalink
  3. LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864} (lnxw48a1@nu.federati.net)'s status on Saturday, 28-Aug-2021 20:58:48 UTC LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864} LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864}
    in reply to
    • Alexandre Oliva
    @lxo I admit I am no expert, but I have not seen a #cryptocurrency based on #git and #gpg.
    In conversation about 3 months ago from mustard permalink
  4. LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864} (lnxw48a1@nu.federati.net)'s status on Tuesday, 01-Jun-2021 07:19:48 UTC LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864} LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864}
    I should find out whether #Darcs and #Pijul have #IRC channels set up for their users. It looks like #Fossil has an unofficial channel (latest info says it is on Freenode). I should also look for #Mercurial and #Git and #Breezy / #Bazaar.
    In conversation about 6 months ago from web permalink
  5. LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864} (lnxw48a1@nu.federati.net)'s status on Sunday, 18-Apr-2021 15:41:27 UTC LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864} LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864}
    in reply to
    • LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864}
    Further info: https://news-web.php.net/php.internals/113838

    And with the presumed compromise of git.php.net, all future development activities will take place on #GitHub.

    #code-hosting #vcs #scm #security #git #php
    In conversation about 8 months ago from mustard permalink

    Attachments

    1. php.internals: Changes to Git commit workflow
  6. LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864} (lnxw48a1@nu.federati.net)'s status on Saturday, 03-Apr-2021 03:02:10 UTC LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864} LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864}
    in reply to
    • GeniusMusing
    @geniusmusing I find #git to be too big and complex for my needs (and arguably for most projects). I know it “won” and even some projects that formerly used another #VCS ( such as Mercurial #hg, #darcs, Bazaar #bzr / Breezy #brz ) are switching.

    In the plans: a very limited #Kallithea install (with git and Mercurial) and #Fossil for Federati ... when I have more funds and energy to devote to getting it going on its own VPS.
    In conversation about 8 months ago from Shoyu permalink
  7. LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864} (lnxw48a1@nu.federati.net)'s status on Saturday, 13-Mar-2021 04:14:54 UTC LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864} LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864}
    in reply to
    • Douglas A. Whitfield
    @musicman I am not sure about Maven or Ant, but they do have a "Git repo on Github":{https://github.com/apache/tomcat} and a "Subersion repo":{http://svn.apache.org/repos/asf/tomcat} see https://tomcat.apache.org/source.html

    #mvn #ant #git #svn #tomcat
    In conversation about 9 months ago from web permalink

    Attachments

    1. apache/tomcat
      Apache Tomcat. Contribute to apache/tomcat development by creating an account on GitHub.
    2. asf - Revision 1887561: /tomcat
    3. Apache Tomcat® - Repository Access
  8. LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864} (lnxw48a1@nu.federati.net)'s status on Monday, 30-Nov-2020 23:43:55 UTC LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864} LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864}
    https://arxiv.org/abs/1311.3903

    A Categorical Theory of Patches

    A formalization of the #Darcs theory of patches. Darcs ( http://darcs.net/ ) is a #DVCS, like #git or #hg or #Fossil, but based around patches.

    #VCS #version-control
    In conversation about a year ago from Shoyu permalink

    Attachments

    1. Darcs - FrontPage
    2. A Categorical Theory of Patches
      When working with distant collaborators on the same documents, one often uses a version control system, which is a program tracking the history of files and helping importing modifications brought by others as patches. The implementation of such a system requires to handle lots of situations depending on the operations performed by users on files, and it is thus difficult to ensure that all the corner cases have been correctly addressed. Here, instead of verifying the implementation of such a system, we adopt a complementary approach: we introduce a theoretical model, which is defined abstractly by the universal property that it should satisfy, and work out a concrete description of it. We begin by defining a category of files and patches, where the operation of merging the effect of two coinitial patches is defined by pushout. Since two patches can be incompatible, such a pushout does not necessarily exist in the category, which raises the question of which is the correct category to represent and manipulate files in conflicting state. We provide an answer by investigating the free completion of the category of files under finite colimits, and give an explicit description of this category: its objects are finite sets labeled by lines equipped with a transitive relation and morphisms are partial functions respecting labeling and relations.
  9. LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864} (lnxw48a1@nu.federati.net)'s status on Monday, 09-Nov-2020 04:54:11 UTC LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864} LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864}
    • Federati Networks
    I think y’all know I favor the #Fossil #SCM / #DVCS over #Git (though I’m giving #Mercurial ( #Hg ) another look as well. I’m resource-constrained as well as energy-limited, but I have been thinking of standing up a miniature software forge for !FNetworks projects and users, likely using Kallithea (which can use both Hg and Git) and also having some Fossil repos (but not as part of a forge).
    In conversation about a year ago from Shoyu permalink
  10. LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864} (lnxw48a1@nu.federati.net)'s status on Tuesday, 03-Nov-2020 04:19:39 UTC LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864} LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864}
    How to publish #git repos that cannot be republished to #GitHub: http://joeyh.name/blog/entry/how_to_publish_git_repos_that_cannot_be_republished_to_github/
    In conversation about a year ago from web permalink

    Attachments

    1. how to publish git repos that cannot be republished to github
  11. LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864} (lnxw48a1@nu.federati.net)'s status on Wednesday, 29-Jul-2020 23:54:28 UTC LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864} LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864}
    Planning to play with #Kallithea https://kallithea-scm.org/ soon. I’m still very much in favor of #Fossil https://fossil-scm.org/home/doc/trunk/www/index.wiki but I’m not rigid about it (the way many #Git and #Github users are). If either Git or #Mercurial ( #Hg ) https://www.mercurial-scm.org/ are appropriate for the situation, I’ll use them.
    In conversation Wednesday, 29-Jul-2020 23:54:28 UTC from Shoyu permalink

    Attachments

    1. Kallithea
      Kallithea, a free software source code management system supporting two leading version control systems, Mercurial and Git.
    2. Mercurial SCM
    3. Fossil: Home
  12. Douglas A. Whitfield (musicman@nu.federati.net)'s status on Tuesday, 05-May-2020 16:54:31 UTC Douglas A. Whitfield Douglas A. Whitfield
    I don't know the details. They haven't made a formal announcement that the hiring freeze is over, but this one from our Alameda office just showed up as a new opening (this one can also be worked from our Minneapolis office)

    Responsibilities:

    Represent Perforce as the first point of contact for customer’s technical requests.
    Review and research customer issues to determine and provide the best resolution.
    Develop and maintain technical expertise in assigned areas of product functionality and utilize it effectively to help customers.
    Resolve database and performance issues.
    Research, document, and escalate cases according to procedure.
    Provide customer driven feedback to functional areas in order to influence process/product improvements.
    Author technical documents on common issues and solutions in order to build the knowledge base.
    Positive attitude - Support engineers are required to be respectful, fair, gracious, and knowledgeable.
    Create and set up test environments to reproduce and resolve customer issues.
    Recreate customer environments to reproduce issues and experiment with possible solutions.

    Requirements:

    Bachelor’s Degree in Computer Science or similar or relevant work experience
    2 or more years’ experience providing technical support to enterprise customers
    Knowledge of C/C++ and Java and experience with #PHP / #MySQL
    Knowledge of Unix & #Linux
    Basic networking experience
    Experience with Perforce, #Git, or other version control software is desirable
    Strong analytics and problem-solving skills
    Strong debugging skills
    Ability to work in a team environment and contribute ideas and improvements
    Able to work well under pressure and prioritize accordingly
    In conversation Tuesday, 05-May-2020 16:54:31 UTC from web permalink
  13. N-5-O-body (n5admin@n5.federati.net)'s status on Sunday, 26-Apr-2020 05:45:07 UTC N-5-O-body N-5-O-body
    Remote profile options...
    in reply to
    • N-5-O-body
    I much prefer #Fossil to #Git.

    I haven't really used #Breezy / #brz ( the actively developed fork of #Bazaar / #bzr ) or #Mercurial / #hg or #Darcs or #Pijul. I should explore some of these.

    Maybe I should see about getting a #Launchpad account.
    In conversation Sunday, 26-Apr-2020 05:45:07 UTC from n5.federati.net permalink
  14. LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864} (lnxw48a1@nu.federati.net)'s status on Thursday, 26-Mar-2020 18:52:43 UTC LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864} LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864}
    in reply to
    • Douglas A. Whitfield
    @musicman Yes, I think #git is overly complicated for most projects' needs, but it has mindshare, so people often demand it when another VCS would be more appropriate. It'd be great if transitioning from one to another was a well-understood problem, but it isn't.

    Is that #Emacs that is trying to move from #svn to git with #ESR's help and having a difficult time of it?
    In conversation Thursday, 26-Mar-2020 18:52:43 UTC from web permalink
  15. Claes Wallin 🇸🇪🇭🇰 (clacke@libranet.de)'s status on Thursday, 09-Jan-2020 13:05:47 UTC Claes Wallin 🇸🇪🇭🇰 Claes Wallin 🇸🇪🇭🇰
    Remote profile options...
    • Drew DeVault
    • Claes Wallin 🇸🇪🇭🇰
    • Matthew Graybosch
    https://mastodon.sdf.org/@starbreaker/103415874085298341

    Judas Priest still rules 🤘
    2020-01-02 21:36:48
    OK. Take a look at <https://sourcehut.org>.

    @sir created this whole toolkit that supports both #git and #mercurial and provides most of the same functionality as services like Github, Gitlab, Gitea, etc. WITHOUT USING JAVASCRIPT.

    You want public repositories? Sourcehut has it. Continuous integration? Wikis? Mailing lists? Patch submission by email? Gist/Pastebin? It's all there.

    There's a hosted version at <https://sr.ht>, and you can self-host instead if you want.

    https://libranet.de/display/268c77b3a659bfa930d604c415b0754068791520
    In conversation Thursday, 09-Jan-2020 13:05:47 UTC from libranet.de permalink

    Attachments

    1. Judas Priest still rules 🤘
      from Judas Priest still rules 🤘
      OK. Take a look at . @sir created this whole toolkit that supports both #git and #mercurial and provides most of the same functionali...
  16. Douglas A. Whitfield (musicman@nu.federati.net)'s status on Saturday, 04-Jan-2020 21:08:53 UTC Douglas A. Whitfield Douglas A. Whitfield
    My team (current, not the one I am moving to) is looking for someone in #Sydney, #Australia. Location is non-negotiable.

    Requirements:
    Bachelor’s Degree in Computer Science or similar or relevant work experience
    2 or more years’ experience providing technical support directly to enterprise customers
    Knowledge of C/C++ and #Java and experience with #PHP/MySQL
    Knowledge of #Unix & #Linux
    Basic networking experience
    Experience with Perforce, #Git, or other version control software is desirable
    Experience in customer support or customer-facing role
    Strong analytics and problem-solving skills
    Strong debugging skills
    Ability to work in a team environment and contribute ideas and improvements
    Able to work well under pressure and prioritize accordingly

    Responsibilities:
    Represent Perforce as the first point of contact for customer’s technical requests.
    Review and research customer issues to determine and provide the best resolution.
    Develop and maintain technical expertise in assigned areas of product functionality and utilize it effectively to help customers.
    Resolve database and performance issues.
    Research, document, and escalate cases according to procedure.
    Provide customer driven feedback to functional areas in order to influence process/product improvements.
    Author technical documents on common issues and solutions in order to build the knowledge base.
    Positive attitude - Support engineers are required to be respectful, fair, gracious, and knowledgeable.
    Create and set up test environments to reproduce and resolve customer issues.
    Recreate customer environments to reproduce issues and experiment with possible solutions.

    Please pass this along to anyone you think might be interested!
    In conversation Saturday, 04-Jan-2020 21:08:53 UTC from web permalink
  17. Douglas A. Whitfield (musicman@nu.federati.net)'s status on Monday, 16-Dec-2019 20:37:34 UTC Douglas A. Whitfield Douglas A. Whitfield
    My team (current, not the one I am moving to) is looking for someone in #Sydney, #Australia. Location is non-negotiable.

    Requirements:
    Bachelor’s Degree in Computer Science or similar or relevant work experience
    2 or more years’ experience providing technical support directly to enterprise customers
    Knowledge of C/C++ and #Java and experience with #PHP/MySQL
    Knowledge of #Unix & #Linux
    Basic networking experience
    Experience with Perforce, #Git, or other version control software is desirable
    Experience in customer support or customer-facing role
    Strong analytics and problem-solving skills
    Strong debugging skills
    Ability to work in a team environment and contribute ideas and improvements
    Able to work well under pressure and prioritize accordingly

    Responsibilities:
    Represent Perforce as the first point of contact for customer’s technical requests.
    Review and research customer issues to determine and provide the best resolution.
    Develop and maintain technical expertise in assigned areas of product functionality and utilize it effectively to help customers.
    Resolve database and performance issues.
    Research, document, and escalate cases according to procedure.
    Provide customer driven feedback to functional areas in order to influence process/product improvements.
    Author technical documents on common issues and solutions in order to build the knowledge base.
    Positive attitude - Support engineers are required to be respectful, fair, gracious, and knowledgeable.
    Create and set up test environments to reproduce and resolve customer issues.
    Recreate customer environments to reproduce issues and experiment with possible solutions.

    Please pass this along to anyone you think might be interested!
    In conversation Monday, 16-Dec-2019 20:37:34 UTC from web permalink
  18. LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864} (lnxw48a1@nu.federati.net)'s status on Monday, 16-Dec-2019 14:22:21 UTC LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864} LinuxWalt (@lnxw48a1) {3EB165E0-5BB1-45D2-9E7D-93B31821F864}
    in reply to
    • Infected Moomin
    @moonman My feelings exactly. I didn't have anything original there ( #Github ) in the first place, but I had patches for others' projects. I removed everything several years ago. Yes, a couple of potential employers have passed on hiring me because my GH account was empty. I just (A) don't want to support centralized facilities like GH or SourceForge any more, when you can host your own #git / #hg / #darcs / fossil; and (B) as my role at work has changed more toward user support, I'm not creating or using such patches any more, so if someone found and started using them, they'd be potentially doing it wrong / importing security holes.

    ( For a while, I had my own #Fossil repo with some original stuff, but thanks to hosting changes are $EMPLOYER work scheduling / hotel Internet, that's all gone, too. )
    In conversation Monday, 16-Dec-2019 14:22:21 UTC from Choqok permalink
  19. Strypey (strypey@mastodon.nzoss.nz)'s status on Tuesday, 10-Dec-2019 22:22:31 UTC Strypey Strypey
    Remote profile options...
    • Wolf480pl

    @Wolf480pl yes, AFAIK issues and wikis on GitLab are #Git repos. I'm not sure if this is what Drew meant by "Git objects", reading it again I'm wondering if he meant making individual tickets and wikipages things that Git can pull and push. Not sure if GL wikis/ tickets are like that, and if they are, it doesn't seem to help with pushing or pulling them between GL instances AFAICT.

    In conversation Tuesday, 10-Dec-2019 22:22:31 UTC from mastodon.nzoss.nz permalink
  20. Douglas A. Whitfield (musicman@nu.federati.net)'s status on Monday, 28-Oct-2019 20:11:27 UTC Douglas A. Whitfield Douglas A. Whitfield
    We're hiring on my team again!

    Nice-to-haves*:
    Knowledge of C/C++ and #Java and experience with #PHP/MySQL
    Knowledge of Unix & #Linux
    Basic networking experience
    Experience with Perforce, #Git, or other version control software is desirable
    Bachelor’s Degree in Computer Science or similar or relevant work experience
    2 or more years’ experience providing technical support directly to enterprise customers

    * These are listed as requirements on the site, but they make zero since to me. There is literally no one on the Minneapolis team that knows C/C++. We do have a C/C++ API, so yes, it would be good if you knew that, but most people use our derived APIs (Perl, Python, .NET, Ruby, PHP, and maybe that is it). Java, like C, is a native API.

    Also, we do support Windows and Mac, so unclear why knowledge of that is not listed.

    Experience in customer support or customer-facing role
    Strong analytics and problem-solving skills
    Strong debugging skills
    Ability to work in a team environment and contribute ideas and improvements
    Able to work well under pressure and prioritize accordingly
    Responsibilities:
    Represent Perforce as the first point of contact for customer’s technical requests.
    Review and research customer issues to determine and provide the best resolution.
    Develop and maintain technical expertise in assigned areas of product functionality and utilize it effectively to help customers.
    Resolve database and performance issues.
    Research, document, and escalate cases according to procedure.
    Provide customer driven feedback to functional areas in order to influence process/product improvements.
    Author technical documents on common issues and solutions in order to build the knowledge base.
    Positive attitude - Support engineers are required to be respectful, fair, gracious, and knowledgeable.
    Create and set up test environments to reproduce and resolve customer issues.
    Recreate customer environments to reproduce issues and experiment with possible solutions.
    In conversation Monday, 28-Oct-2019 20:11:27 UTC from web permalink
  • Before

Feeds

  • Activity Streams
  • RSS 1.0
  • RSS 2.0
  • Atom
  • Help
  • About
  • FAQ
  • TOS
  • Privacy
  • Source
  • Version
  • Contact

Federati Nu: Federated N-series GNU Social is a social network, courtesy of Federati Networks. It runs on GNU social, version 2.0.0-dev, available under the GNU Affero General Public License.

Creative Commons Attribution 3.0 All Federati Nu: Federated N-series GNU Social content and data are available under the Creative Commons Attribution 3.0 license.

Switch to mobile site layout.